[jbossws-issues] [JBoss JIRA] Updated: (JBWS-2741) Remove JAXWS API interfaces from jbossws-native-jaxws

Alessio Soldano (JIRA) jira-events at lists.jboss.org
Tue Sep 22 08:26:49 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBWS-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alessio Soldano updated JBWS-2741:
----------------------------------

    Summary: Remove JAXWS API interfaces from jbossws-native-jaxws  (was: Evaluate removal of JAXWS API interfaces from jbossws-native-jaxws)


> Remove JAXWS API interfaces from jbossws-native-jaxws
> -----------------------------------------------------
>
>                 Key: JBWS-2741
>                 URL: https://jira.jboss.org/jira/browse/JBWS-2741
>             Project: JBoss Web Services
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-native
>            Reporter: Alessio Soldano
>            Assignee: Richard Opalka
>             Fix For: jbossws-native-3.2.1
>
>
> At the current state there's probably no more reason for shipping the jaxws api inside the jbossws-native-jaxws instead of using the "official" jaxws api artifact. We might keep the jbossws-native-jaxws just for the service loads (the javax.xml.ws.spi.Provider for instance). This would simplify the m2 dependencies of projects referring to jaxws stuff (for instance jboss ejb3 client requires the jaxws api, but it's not good having that reference the jbossws-native-jaxws when using native and the jaxws-api when using metro/cxf stack).
> This need to be evaluated (both with jdk1.5 and jdk1.6), then changes to code, poms, manifests etc. can be done.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbossws-issues mailing list