[jbossws-issues] [JBoss JIRA] (JBWS-3281) Create a migration guide to JBossWS 4.0 / AS 7 integration

[Alessio Soldano (Updated) (JIRA)]

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

Alessio Soldano updated JBWS-3281:
----------------------------------

    Fix Version/s:  jbossws-cxf-4.0
      Component/s: jbossws-cxf
                   jbossws-native
                       (was: jbossws-metro)
                       (was: jaxws-tools-maven-plugin)

    
> Create a migration guide to JBossWS 4.0 / AS 7 integration
> ----------------------------------------------------------
>
>                 Key: JBWS-3281
>                 URL: https://issues.jboss.org/browse/JBWS-3281
>             Project: JBoss Web Services
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf, jbossws-native, productivity
>            Reporter: Alessio Soldano
>             Fix For: jbossws-native-4.0,  jbossws-cxf-4.0
>
>
> A migration guide from JBossWS 3.4.x to JBossWS 4.0 (and in particular to AS7 w/ JBossWS 4) should be included in the release documentation.
> At the moment the topic to be covered should be:
> - consequences for users due to changes in classloading (see JBossWS AS7 FAQ)
> - changes in API (new jbossws-api library, package refactorings, etc.)
> - @WebContext(virtualHosts) -> @WebContext(virtualHost) change
> - changes in WS-* configuration
> - changes due to libraries upgrades (mainly due to dependencies coming from Apache CXF 2.4 upgrade)
> - new descriptor(s) (jboss-webservices.xml)

--
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