: In testing Solr 1.4 today with Weblogic it looks like the filters issue still : exists. Adding the appropriate entries in weblogic.xml still resolves it. : : Would it make sense to include a weblogic.xml in the distribution to disable : the filters or should this be an exercise for users/administrators who chose : to deploy this under weblogic?
Ilan: It's been a long time since i tried using weblogic ... when you talk about adding a weblogic.xml file to prevent this bug, were any other changes to the web.xml file required? (I was under the impression that you had to remove the Servlet Filter mapping from web.xml and use weblogic specific options when declaring it in weblogic.xml ... but your description makes me think i completley missunderstood before) If it's possible to have a simple weblogic.xml file that can be droped into the solr.war and will make solr work on weblogic out of the box (without adversely affecting any other servlet containers) then by all means please open a bug and attach a patch containing the weblogic.xml file and mark "fix for 1.4" since this seems like an easy thing to get inot the 1.4 release -- assuming you're willing to help test it. -Hoss
