[jbossws-issues] [JBoss JIRA] (JBWS-3396) Evaluate partial generation of jbossws-cxf.xml descriptor

[Alessio Soldano (JIRA)]

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

Alessio Soldano commented on JBWS-3396:
---------------------------------------

The latest agreed idea for dealing with the issue here (when an "incomplete" jbossws-cxf.xml is provided) would be to generate a parent jbws-cxf.xml spring context using the metadata (coming from annotated endpoint classes / web.xml) and let the user provided jbossws-cxf.xml be a child of that parent. We'd also check for duplicated jaxws:endpoint declarations, and let the provided file ones override those from metadata (so basically exclude them from generated file).
                
> Evaluate partial generation of jbossws-cxf.xml descriptor
> ---------------------------------------------------------
>
>                 Key: JBWS-3396
>                 URL: https://issues.jboss.org/browse/JBWS-3396
>             Project: JBoss Web Services
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf
>            Reporter: Alessio Soldano
>            Assignee: Jim Ma
>
> See http://community.jboss.org/message/640779#640779 . Basically the issue with the need for user to specify every endpoint in the jbossws-cxf.xml, while in some case the info might come from the metadata created from the web.xml / annotations. At least we could have defaults.
> The same applies to defaults for the address attribute in jaxws:endpoint.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira