Return-Path: 
 <solr-user-return-13564-apmail-lucene-solr-user-archive=lucene.apache.org@lucene.apache.org>
Delivered-To: apmail-lucene-solr-user-archive@locus.apache.org
Received: (qmail 99648 invoked from network); 8 Sep 2008 07:58:36 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 8 Sep 2008 07:58:36 -0000
Received: (qmail 96216 invoked by uid 500); 8 Sep 2008 07:58:31 -0000
Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org
Received: (qmail 96059 invoked by uid 500); 8 Sep 2008 07:58:31 -0000
Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:solr-user-help@lucene.apache.org>
List-Unsubscribe: <mailto:solr-user-unsubscribe@lucene.apache.org>
List-Post: <mailto:solr-user@lucene.apache.org>
List-Id: <solr-user.lucene.apache.org>
Reply-To: solr-user@lucene.apache.org
Delivered-To: mailing list solr-user@lucene.apache.org
Received: (qmail 96048 invoked by uid 99); 8 Sep 2008 07:58:31 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Sep 2008 00:58:31 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: local policy)
Received: from [194.12.217.13] (HELO relay6.guj.de) (194.12.217.13)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Sep 2008 07:57:30 +0000
Received: from smtp3.ps.guj.de (smtp3.ps.guj.de [194.12.199.41])
	by relay6.guj.de (8.13.1/guj-zz-1.8f3er) with ESMTP id m887vTNq029829
	for <solr-user@lucene.apache.org>; Mon, 8 Sep 2008 09:57:29 +0200
Received: from hamgujexc032.global.intra.guj.com
 (hamgujexc032.global.intra.guj.com [194.12.204.152])
	by smtp3.ps.guj.de (8.13.1p3/guj-zz-1.8.3ibr) with ESMTP id m887vTMd025305
	for <solr-user@lucene.apache.org>; Mon, 8 Sep 2008 09:57:29 +0200 (CEST)
Received: from hamgujexc005.global.intra.guj.com ([194.12.204.145]) by
 hamgujexc032.global.intra.guj.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 8 Sep 2008 09:57:30 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: AW: Cross-context-forward to solr-instance
Date: Mon, 8 Sep 2008 09:57:29 +0200
Message-ID: 
 <E337D5BC2EE973448ECBA70100E6FCB60418E8B7@hamgujexc005.global.intra.guj.com>
In-Reply-To: 
 <E337D5BC2EE973448ECBA70100E6FCB60418E884@hamgujexc005.global.intra.guj.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Cross-context-forward to solr-instance
Thread-Index: AckP5e0F/iktbonfTMK2yrHRlxAPZwBonJsQ
References: 
 <E337D5BC2EE973448ECBA70100E6FCB60418E884@hamgujexc005.global.intra.guj.com>
From: "Hachmann, Bjoern" <hachmann.bjoern@guj.de>
To: <solr-user@lucene.apache.org>
X-OriginalArrivalTime: 08 Sep 2008 07:57:30.0025 (UTC)
 FILETIME=[8AE4E190:01C91188]
X-TM-AS-Product-Ver: SMEX-8.0.0.1259-5.500.1027-16144.005
X-TM-AS-Result: No--17.856800-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
X-Virus-Checked: Checked by ClamAV on apache.org

Hi,

I made a mistake. At least with Tomcat 5.5.x, if you configure the =
SolrRequestFilter with <dispatcher>FORWARD</dispatcher> it indeed gets =
called even when you forward from another web-context!=20

Note, that the documentation says this might be problematic!

Sorry for the previous overhasty post.
Bj=F6rn

> -----Urspr=FCngliche Nachricht-----
> Von:=20
> solr-user-return-13537-hachmann.bjoern=3Dguj.de@lucene.apache.or
> g=20
> [mailto:solr-user-return-13537-hachmann.bjoern=3Dguj.de@lucene.a
pache.org] Im Auftrag von Hachmann, Bjoern
> Gesendet: Samstag, 6. September 2008 08:01
> An: solr-user@lucene.apache.org
> Betreff: Cross-context-forward to solr-instance
>=20
> Hi,=20
> =20
> yesterday I tried the Solr-1.3-RC2 and everything seems to=20
> work fine using the traditional single-core setup. But while=20
> troubleshooting the new multi-core feature, I realized for=20
> the first time, that I have been using the deprecated (even=20
> in 1.2) class SolrServlet. This is a huge problem for us, as=20
> we run the solr-web-app parallel to our main web-app in the=20
> same servlet-container. Using this approach we can internally=20
> forward update- and select-requests to the Solr-instance=20
> currently in use.=20
> =20
> ServletContext ctx =3D getServletContext().getContext("solr1");
> RequestDispatcher rd =3D ctx.getNamedDispatcher("SolrServer");
> rd.forward(request, response);
>=20
> As you can see, this approach only works for the servlet=20
> named 'SolrServer' which references the deprecated class.=20
>=20
> The attempt of using a path based dispatcher=20
> (ctx.getRequestDispatcher) was not successful, even though I=20
> configured the SolrRequestFilter in the solr-web.xml to work=20
> on forwards (<dispatcher>FORWARD</dispatcher>), which the=20
> documentation discourages. Maybe this is because of the=20
> cross-context-dispatch?
>=20
> At the moment I ran totally out of ideas, apart from=20
> completely redesigning our whole setup. Any ideas are highly=20
> appreciated.=20
>=20
> Thanks in advance,
> Bj=F6rn