[jbossws-issues] [JBoss JIRA] Commented: (JBWS-3286) Add jaxws-endpoint-configuration to AS7 domain
[
https://issues.jboss.org/browse/JBWS-3286?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on JBWS-3286:
---------------------------------------
A proposal of change to the ws subsystem schema would be:
--- a/webservices/server-integration/src/main/resources/schema/jboss-webservices.xsd
+++ b/webservices/server-integration/src/main/resources/schema/jboss-webservices.xsd
@@ -24,10 +24,13 @@
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="urn:jboss:domain:webservices:1.0"
xmlns="urn:jboss:domain:webservices:1.0"
+ xmlns:jaxwsconfig="urn:jboss:jbossws-jaxws-config:4.0"
elementFormDefault="qualified"
attributeFormDefault="unqualified"
version="1.0">
+ <xs:import namespace="urn:jboss:jbossws-jaxws-config:4.0"
schemaLocation="jbossws-jaxws-config_4_0.xsd"/>
+
<!-- The webservices subsystem root element -->
<xs:element name="subsystem" type="webservices-containerType"
/>
@@ -42,6 +45,7 @@
</xs:annotation>
<xs:sequence>
<xs:element minOccurs="1" maxOccurs="1"
name="configuration" type="serverConfigType" />
+ <xs:element minOccurs="0" maxOccurs="unbounded"
name="jaxws-endpoint-configuration"
type="jaxwsconfig:endpointConfigType" />
</xs:sequence>
</xs:complexType>
with the jbossws-jaxws-config_4_0.xsd being an exact copy of the xsd in jbossws-spi.
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
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira