[
https://issues.apache.org/jira/browse/CMIS-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424786#comment-13424786
]
Florian Müller commented on CMIS-543:
-------------------------------------
This file is necessary for all containers that do not use the JAX-WS RI by
default. If, for example, the default JAX-WS implementation is CXF, OpenCMIS
will not work properly. Depending on the container and its classloader magic,
the javax.xml.ws.spi.Provider file has to be in this jar.
The OpenCMIS Web Services binding will not work in JBoss without the JAX-WS RI!
The reason for this that are deficiencies in JAX-WS specification that have to
be compensated with proprietary API calls. The code that calls these APIs has
been written for the JAX-WS RI. It is possible to do the same for CXF and other
frameworks, but nobody has written this code so far.
> Remove /META-INF/services/javax.xml.ws.spi.Provider
> ---------------------------------------------------
>
> Key: CMIS-543
> URL: https://issues.apache.org/jira/browse/CMIS-543
> Project: Chemistry
> Issue Type: Improvement
> Components: opencmis-client-bindings
> Affects Versions: OpenCMIS 0.6.0
> Environment: Weblogic 10.3.2 and 10.3.5
> Reporter: Ron DiFrango
> Assignee: Florian Müller
> Priority: Blocker
>
> It seems as if the presence of the file:
> /META-INF/services/javax.xml.ws.spi.Provider
> Causes other Weblogic JAX-WS client services to break with an exception. A
> custom Weblogic implementation jar needs to be created that address the
> streaming problem of JAX-WS but doesn't cause the NPE to happen in Weblogic.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
