[jbossws-issues] [JBoss JIRA] (JBWS-3413) java.xml.ws.spi.Provider resolution is JVM implementation specific

Alessio Soldano (JIRA) jira-events at lists.jboss.org
Tue Jan 24 17:22:18 EST 2012


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

Alessio Soldano commented on JBWS-3413:
---------------------------------------

https://github.com/jbossas/jboss-as/pull/1207
                
> java.xml.ws.spi.Provider resolution is JVM implementation specific
> ------------------------------------------------------------------
>
>                 Key: JBWS-3413
>                 URL: https://issues.jboss.org/browse/JBWS-3413
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf
>            Reporter: Alessio Soldano
>            Assignee: Alessio Soldano
>            Priority: Critical
>             Fix For: jbossws-cxf-4.0.1
>
>
> The javax.xml.ws.spi.Provider resolution is based on the ServiceLoader.load(Provider.class) internals. That makes it JVM specific due to the different implementation of collections used to store the found resources.
> This is critical as the jbossws-cxf client Provider impl is responsible for setting the proper thread Bus, ensuring proper deployment isolation.
> We need to prevent potential issues (especially with IBM JDK) by avoiding duplicates of META-INF/services/javax.xml.ws.spi.Provider (Apache CXF one vs JBossWS-CXF one).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbossws-issues mailing list