[jboss-jira] [JBoss JIRA] Commented: (JBEE-75) Provide JAXWS api that uses AS7 module classloading

[Shelly McGowan (JIRA)]

    [ https://issues.jboss.org/browse/JBEE-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584554#comment-12584554 ] 

Shelly McGowan commented on JBEE-75:
------------------------------------

A 2.0.0.Alpha1 version of the APIs were released:
https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/javax/xml/ws/jboss-jaxws-api_2.2_spec/2.0.0.Alpha1/

> Provide JAXWS api that uses AS7 module classloading
> ---------------------------------------------------
>
>                 Key: JBEE-75
>                 URL: https://issues.jboss.org/browse/JBEE-75
>             Project: JBoss JavaEE APIs
>          Issue Type: Feature Request
>            Reporter: Alessio Soldano
>            Assignee: Shelly McGowan
>
> Our version of JAXWS api uses the original mechanisms for detecting the javax.xml.ws.spi.Provider class to use and create a new instance of.
> On AS7 we need to hide our implementations from the client runtime classpath; as a result of that we can't "pollute" the thread context classloader with the jbossws / cxf / etc. impl jars, so the JAXWS api Provider impl detection (that is based upon service loader) won't work properly.
> Moreover, there's likely to be a requirement for supporting the option of users overriding the JAXWS provider impl to use in a given deployment.
> So, our jaxws api should be able (at least) to dynamically load the jbossws jaxws client implementation module (without affecting the TCCL) and use that for resolving the javax.xml.ws.spi.Provider to use.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira