Return-Path: 
 <solr-dev-return-20350-apmail-lucene-solr-dev-archive=lucene.apache.org@lucene.apache.org>
Delivered-To: apmail-lucene-solr-dev-archive@minotaur.apache.org
Received: (qmail 57623 invoked from network); 26 Sep 2009 19:56:48 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 26 Sep 2009 19:56:48 -0000
Received: (qmail 96743 invoked by uid 500); 26 Sep 2009 19:56:48 -0000
Delivered-To: apmail-lucene-solr-dev-archive@lucene.apache.org
Received: (qmail 96675 invoked by uid 500); 26 Sep 2009 19:56:47 -0000
Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:solr-dev-help@lucene.apache.org>
List-Unsubscribe: <mailto:solr-dev-unsubscribe@lucene.apache.org>
List-Post: <mailto:solr-dev@lucene.apache.org>
List-Id: <solr-dev.lucene.apache.org>
Reply-To: solr-dev@lucene.apache.org
Delivered-To: mailing list solr-dev@lucene.apache.org
Received: (qmail 96665 invoked by uid 99); 26 Sep 2009 19:56:47 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Sep 2009 19:56:47 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Sep 2009 19:56:36 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 0794B234C004
	for <solr-dev@lucene.apache.org>; Sat, 26 Sep 2009 12:56:16 -0700 (PDT)
Message-ID: <1687069780.1253994976016.JavaMail.jira@brutus>
Date: Sat, 26 Sep 2009 12:56:16 -0700 (PDT)
From: "Hoss Man (JIRA)" <jira@apache.org>
To: solr-dev@lucene.apache.org
Subject: [jira] Commented: (SOLR-1448) Addition of weblogic.xml required for
 solr to run under weblogic 10.3
In-Reply-To: <71363403.1253489057036.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/SOLR-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759939#action_12759939 ] 

Hoss Man commented on SOLR-1448:
--------------------------------

Grant: I don't understand your objection to this addition.  It makes solr work in weblogic by default (currently it will only work if people manually hack the war) and it doesn't have any impact on any other servlet containers.

If we're going to do things like SOLR-1091 to work around odd behavior in specific containers, why wouldn't we do this as well?


> Addition of weblogic.xml required for solr to run under weblogic 10.3
> ---------------------------------------------------------------------
>
>                 Key: SOLR-1448
>                 URL: https://issues.apache.org/jira/browse/SOLR-1448
>             Project: Solr
>          Issue Type: Improvement
>          Components: web gui
>    Affects Versions: 1.4
>         Environment: Weblogic 10.3
>            Reporter: Ilan Rabinovitch
>            Priority: Minor
>             Fix For: 1.4
>
>         Attachments: weblogic.xml
>
>
> Weblogic appears to have filters enabled even on FORWARD, which is listed as something that will not function properly in the Solr documentation. As a result, the administrative application generates a StackOverflow when accessed. 
> This can be resolved by adding the attached weblogic.xml file to solr.  No other changes are required.
> <?xml version='1.0' encoding='UTF-8'?>
> <weblogic-web-app
>     xmlns="http://www.bea.com/ns/weblogic/90"
>     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>     xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
>     <container-descriptor>
>         <filter-dispatched-requests-enabled>false</filter-dispatched-requests-enabled>
>     </container-descriptor>
> </weblogic-web-app>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.