Following up on this question with the resolution. Packaging the application as an ear instead of a war allowed the deployment to work on WebLogic 12c. In weblogic-application.xml the "prefer-application-packages" can be used. Also, the weblogic.xml file needed prefer-web-inf-classes set to true. These two modifications worked in our case.
weblogic.xml <?xml version = '1.0' encoding = 'windows-1252'?> <weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.5/weblogic-web-app.xsd"; xmlns="http://xmlns.oracle.com/weblogic/weblogic-web-app";> <container-descriptor> <prefer-web-inf-classes>true</prefer-web-inf-classes> </container-descriptor> </weblogic-web-app> Weblogic-application.xml <?xml version = '1.0' encoding = 'windows-1252'?> <weblogic-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.5/weblogic-application.xsd"; xmlns="http://xmlns.oracle.com/weblogic/weblogic-application";> <prefer-application-packages> <package-name>com.ctc.*</package-name> <package-name>com.sun.xml.*</package-name> <package-name>com.sun.istack.*</package-name> <package-name>com.sun.msv.datatype.*</package-name> <package-name>com.sun.msv.driver.*</package-name> <package-name>com.sun.msv.grammar.*</package-name> <package-name>com.sun.msv.reader.*</package-name> <package-name>com.sun.msv.relaxns.*</package-name> <package-name>com.sun.msv.scanner.*</package-name> <package-name>com.sun.msv.util.*</package-name> <package-name>com.sun.msv.verifier.*</package-name> <package-name>com.sun.msv.writer.*</package-name> <package-name>com.sun.org.apache.xml.internal.*</package-name> <package-name>com.sun.wsit.*</package-name> <!--<package-name>javax.jws.*</package-name>--> <!-- <package-name>javax.xml.bind.*</package-name>--> <!-- <package-name>javax.xml.soap.*</package-name>--> <!--<package-name>javax.xml.stream.*</package-name>--> <!--<package-name>javax.xml.ws.*</package-name>--> <package-name>javax.xml.activation.*</package-name> <package-name>javax.xml.annotation.*</package-name> <package-name>javax.xml.mail.*</package-name> <package-name>javax.xml.security.*</package-name> <package-name>javax.xml.registry.*</package-name> <package-name>javax.xml.rpc.*</package-name> <package-name>javax.xml.crypto.*</package-name> <package-name>org.apache.xerces.*</package-name> <package-name>javanet.staxutils.*</package-name> <package-name>jp.gr.xml.*</package-name> <package-name>org.codehaus.stax2.*</package-name> <package-name>org.glassfish.gmbal.*</package-name> <package-name>org.iso_relax.*</package-name> <package-name>org.jcp.xml.dsig.*</package-name> <package-name>org.jvnet.*</package-name> <package-name>org.relaxng.*</package-name> </prefer-application-packages> </weblogic-application> -----Original Message----- From: Florian Müller [mailto:f...@apache.org] Sent: Monday, August 24, 2015 9:23 AM To: dev@chemistry.apache.org Cc: Peter Flies Subject: Re: OpenCMIS on WebLogic 12 Hi Peter, It should be possible to configure WebLogic 12 to use the JAX-WS stack that is bundled with an application instead of it's own. Maybe someone on this list can help. The next release of OpenCMIS will use Apache CXF 3.0.x. So, you have to do something like this anyway. There is no fixed date for the next release. We release when the community thinks it's time for another release. There haven't been any discussions about the next release, yet. - Florian > Following the OpenCMIS development guide, we have been able to create > a server that works with Web Services on Tomcat. It appears that > OpenCMIS requires the JAX-WS lib 2.1.7. However, on WebLogic 12, a > later version is used for JAX-WS and the web services fail. > > > > Can the OpenCMIS server work with newer versions of JAX-WS at this > time? If not, what is the roadmap for versions beyond 0.13.0? > > > > Thanks > > > > Peter
