[ 
https://issues.apache.org/jira/browse/SOLR-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cassandra Targett closed SOLR-5534.
-----------------------------------
    Resolution: Won't Fix

Solr no longer supports web containers as of v5, and it's unlikely any fixes 
will be made for 4.x or earlier versions.

https://wiki.apache.org/solr/WhyNoWar

> weblogic.xml doesn't work for WL 12c.
> -------------------------------------
>
>                 Key: SOLR-5534
>                 URL: https://issues.apache.org/jira/browse/SOLR-5534
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.5.1
>            Reporter: Ilia Naryzhny
>            Priority: Minor
>              Labels: weblogic
>
> Provided weblogic.xml work incorrectly with WebLogic. The main reason: 
> providing of Guava classes by weblogic themself. Weblogic's version is 
> conflicting with Solr. Recommend to update this class to: 
> <?xml version="1.0" encoding="UTF-8"?>
> <wls:weblogic-web-app
> xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-web-app";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
> http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd
> http://xmlns.oracle.com/weblogic/weblogic-web-app
> http://xmlns.oracle.com/weblogic/weblogic-web-app/1.4/weblogic-web-app.xsd";>
>      <wls:weblogic-version>12.1.1</wls:weblogic-version>
>      <wls:context-root>solr</wls:context-root>
>      <wls:container-descriptor>
>        
> <wls:filter-dispatched-requests-enabled>false</wls:filter-dispatched-requests-enabled>
>          <wls:prefer-application-packages>
>              <wls:package-name>com.google.common</wls:package-name>
>          </wls:prefer-application-packages>
>      </wls:container-descriptor>
> </wls:weblogic-web-app>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to