[jbossws-issues] [JBoss JIRA] (JBWS-3287) Deployment descriptor support for declaring jbossws-config-file / jbossws-config-name

[Alessio Soldano (JIRA)]

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

Alessio Soldano updated JBWS-3287:
----------------------------------

    Fix Version/s:     (was: jbossws-native-4.1)
      Component/s:     (was: jbossws-native)


Removing jbossws-native component and fix version as native stack reached EOL.
                
> Deployment descriptor support for declaring jbossws-config-file / jbossws-config-name
> -------------------------------------------------------------------------------------
>
>                 Key: JBWS-3287
>                 URL: https://issues.jboss.org/browse/JBWS-3287
>             Project: JBoss Web Services
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf, jbossws-integration
>            Reporter: Alessio Soldano
>             Fix For: jbossws-cxf-4.1
>
>
> The jaxws endpoint configuration is currently declared through the @EndpointConfig annotation. The jbossws-native used to support declaring the same through context-params in the servlet web.xml. We should allow the same (perhaps even for ejb descriptor).
> For the jbws-cxf stack that probably implies early looking at the parameters when creating/rewriting the web.xml, as the endpoint publish (which needs those params) happens at bus startup in BusDeploymentAspect (deploy time, not runtime / when the endpoint servlet is first called)

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