[
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.
