[jbossws-issues] [JBoss JIRA] Updated: (JBWS-3286) Add jaxws-endpoint-configuration to AS7 domain

[Alessio Soldano (JIRA)]

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

Alessio Soldano updated JBWS-3286:
----------------------------------

    Description: 
This feature request is about adding support for jaxws endpoint configurations to the AS7 domain model. We used to have them in the standard-jaxws-endpoint.xml file before AS7 and for jbossws-native only. Now, after JBWS-3282 work, we do have a stack agnostic jaxws endpoint configuration concept. jbossws-spi has the xsd and parser for that. Currently @EndpointConfig can be used to reference a descriptor provided with the deployment and containing the endpoint configuration to be used. If the annotation is not specified, jbossws-native defaults to the contents of standard-jaxws-endpoint.xml, while jbossws-cxf defaults to no configuration (see org.jboss.wsf.stack.cxf.metadata.MetadataBuilder::configureEndpoint(..) ).
So we need to:
1) expose a mean of getting the default jaxws endpoint configurations in jbossws-spi
2) use that in jbossws-cxf MetadataBuilder and in jbossws-native org.jboss.ws.metadata.config.JBossWSConfigFactory
3) actually add the jaxws-endpoint-configuration to AS7 detyped model

In terms of AS7 management, it should be possible to add/delete/modify a given default jaxws endpoint configuration. An all-or-nothing update policy might make sense for the contents of the handlers section of each endpoint configuration.

  was:
This feature request is about adding support for jaxws endpoint configurations to the AS7 domain model. We used to have them in the standard-jaxws-endpoint.xml file before AS7 and for jbossws-native only. Now, after JBWS-3282 work, we do have a stack agnostic jaxws endpoint configuration concept. jbossws-spi has the xsd and parser for that. Currently @EndpointConfig can be used to reference a descriptor provided with the deployment and containing the endpoint configuration to be used. If the annotation is not specified, jbossws-native defaults to the contents of standard-jaxws-endpoint.xml, while jbossws-cxf defaults to no configuration (see org.jboss.wsf.stack.cxf.metadata.MetadataBuilder::configureEndpoint(..) ).
So we need to:
1) expose a mean of getting the default jaxws endpoint configurations in jbossws-spi
2) use that in jbossws-cxf MetadataBuilder and in jbossws-native org.jboss.ws.metadata.config.JBossWSConfigFactory
3) actually add the jaxws-endpoint-configuration to AS7 detyped model



> Add jaxws-endpoint-configuration to AS7 domain
> ----------------------------------------------
>
>                 Key: JBWS-3286
>                 URL: https://issues.jboss.org/browse/JBWS-3286
>             Project: JBoss Web Services
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf, jbossws-integration, jbossws-native
>            Reporter: Alessio Soldano
>            Assignee: Jim Ma
>             Fix For: jbossws-native-4.0,  jbossws-cxf-4.0
>
>
> This feature request is about adding support for jaxws endpoint configurations to the AS7 domain model. We used to have them in the standard-jaxws-endpoint.xml file before AS7 and for jbossws-native only. Now, after JBWS-3282 work, we do have a stack agnostic jaxws endpoint configuration concept. jbossws-spi has the xsd and parser for that. Currently @EndpointConfig can be used to reference a descriptor provided with the deployment and containing the endpoint configuration to be used. If the annotation is not specified, jbossws-native defaults to the contents of standard-jaxws-endpoint.xml, while jbossws-cxf defaults to no configuration (see org.jboss.wsf.stack.cxf.metadata.MetadataBuilder::configureEndpoint(..) ).
> So we need to:
> 1) expose a mean of getting the default jaxws endpoint configurations in jbossws-spi
> 2) use that in jbossws-cxf MetadataBuilder and in jbossws-native org.jboss.ws.metadata.config.JBossWSConfigFactory
> 3) actually add the jaxws-endpoint-configuration to AS7 detyped model
> In terms of AS7 management, it should be possible to add/delete/modify a given default jaxws endpoint configuration. An all-or-nothing update policy might make sense for the contents of the handlers section of each endpoint configuration.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira