Hi Florian, it works also in principle in our setup with axis2. But we are in trouble with OutOfMemory exceptions (GC limit reached) due to unreleasable references in old gen. Analysis of heap dump shows that a major part of heap are occupied by axis2 objects. So I tried to switch WS library to CXF in order to get a work around for this behavior.
Could you give me informations what possibilities I have to avoid the web service binding? Martin -----Ursprüngliche Nachricht----- Von: Florian Müller [mailto:f...@apache.org] Gesendet: Sonntag, 21. Februar 2016 17:41 An: dev@chemistry.apache.org Cc: Brockmann, Martin (IT.NRW) Betreff: Re: AW: AW: Missing Source Hi Martin, I've no experience with your setup, but I seen no reason why it shouldn't work. OpenCMIS tries to determine which JAX-WS implementation to use. That may fail in your environment. You can force a JAX-WS implementation with the session parameter WEBSERVICES_JAXWS_IMPL (valid values are "sunri", "sunjre", "cxf", and "axis2"). Btw. Avoid the web services binding if you can. - Florian > Hi Florian, > > for clarification: I'm running web applications (war) in a JBoss > Server which request a repository via via OpenCMIS. Therefore I use > the OpenCMIS client libraries for these requests. > > In order to provide the OpenCMIS framework for different application > artefacts in the JBoss container I tried to configure them as global > module and not in each application WEB-INF/lib directory. In that > purpose I got the exception mentioned in my first mail. > > Are there any experiences for that purpose? > > - Martin > > > -----Ursprüngliche Nachricht----- > Von: Florian Müller [mailto:f...@apache.org] > Gesendet: Freitag, 19. Februar 2016 18:08 > An: dev@chemistry.apache.org > Cc: Brockmann, Martin (IT.NRW) > Betreff: Re: AW: Missing Source > > Hi Martin, > > No, there is no release date for OpenCMIS 0.14, yet. > > On the server side, OpenCMIS 0.13 and earlier only support the Sun > JAX-WS RI. Starting with OpenCMIS 0.14 only CXF will be supported. We > had to change the JAX-WS implementation because of issues with Java 8. > On the client side, OpenCMIS 0.13 support the RI, the JRE JAX-WS, CXF, > and Axis. OpenCMIS 0.14 will cut this to CXF only. The RI and the JRE > JAX-WS support will removed because of Java 8 problems and the Axis > support will be removed because nobody maintains it. > > - Florian > > >> Hi Florian, >> >> thanks for your reply. >> >> Do you have any informations concerning the release date of OpenCMIS >> 0.14? >> >> I saw comments in the OpenCMIS Axis2 implementation class that it's in >> an "experimental" state. Currently we are using Axis2 1.6.2 in a Java >> EE environment having trouble with gc limit exceptions at high load. >> What's your SPI recommendation for OpenCMIS 0.13? Axis2 in a new >> release or SunJRE? >> >> - Martin >> >> >> -----Ursprüngliche Nachricht----- >> Von: Florian Müller [mailto:f...@apache.org] >> Gesendet: Freitag, 19. Februar 2016 16:50 >> An: dev@chemistry.apache.org >> Cc: Brockmann, Martin (IT.NRW) >> Betreff: Re: Missing Source >> >> Hi Martin, >> >> The JAXB classes are generated. Run a Maven build and the package with >> the sources will appear. >> The OpenCMIS server framework 0.13.0 does not work with CXF. Don't >> spent >> any time looking into it. >> OpenCMIS 0.14.0, on the other hand, only works with CXF. If you want >> play with it, get the latest sources from SVN. >> >> >> - Florian >> >> >>> Hello, >>> >>> the download of source release 0.13 doesn't contain package >>> org.apache.chemistry.opencmis.commons.impl.jaxb. >>> >>> I've got an exception in class RepositoryServicePort using Chemistry >>> with CXF and would like to take a look what's going on there: >>> javax.xml.ws.WebServiceException: Service endpoint interface class >>> org.apache.chemistry.opencmis.commons.impl.jaxb.RepositoryServicePort >>> does not have a javax.jws.WebService annotation. >>> >>> Kind regards >>> Martin
