[
https://issues.jboss.org/browse/AS7-3324?page=com.atlassian.jira.plugin.s...
]
Alessio Soldano updated AS7-3324:
---------------------------------
Description:
The EndpointPublisher spi currently allows for providing @WebService/@WebServiceProvider
annotated endpoint class and deploy endpoint(s) to the running JBoss AS container with an
api pretty much equivalent to the JAXWS Endpoint.publish(..) api. What is missing is the
ability of doing something like:
{code}
List<Source> metadata = new ArrayList<Source>();
StreamSource source = WSDLUtil.getStream(_config.getWsdl());
metadata.add(source);
Map<String, Object> properties = new HashMap<String, Object>();
properties.put(Endpoint.WSDL_SERVICE, portName.getServiceQName());
properties.put(Endpoint.WSDL_PORT, portName.getPortQName());
properties.put(WSDL_LOCATION, WSDLUtil.getURL(_config.getWsdl()).toExternalForm());
...
_endpoint = Endpoint.create(wsProvider); // instance of @WebServiceProvider annotated
class, with no attributes in the annotation
_endpoint.setMetadata(metadata);
_endpoint.setProperties(properties);
_endpoint.publish(publishUrl);
{code}
IOW, we need support for setting properties and metadata and passing them down to the
stack (Apache CXF already reads them from the generated DDBeans/descriptor).
This is required for a proper SwitchYard integration into AS7.
was:
The EndpointPublisher spi currently allows for providing @WebService/@WebServiceProvider
annotated endpoint class and deploy endpoint(s) to the running JBoss AS container with an
api pretty much equivalent to the JAXWS Endpoint.publish(..) api. What is missing is the
ability of doing something like:
{code}
List<Source> metadata = new ArrayList<Source>();
StreamSource source = WSDLUtil.getStream(_config.getWsdl());
metadata.add(source);
Map<String, Object> properties = new HashMap<String, Object>();
properties.put(Endpoint.WSDL_SERVICE, portName.getServiceQName());
properties.put(Endpoint.WSDL_PORT, portName.getPortQName());
properties.put(WSDL_LOCATION, WSDLUtil.getURL(_config.getWsdl()).toExternalForm());
...
_endpoint = Endpoint.create(wsProvider); // instance of @WebServiceProvider annotated
class, with no attributes in the annotation
_endpoint.setMetadata(metadata);
_endpoint.setProperties(properties);
_endpoint.publish(publishUrl);
{code}
IOW, we need support for setting properties and metadata and passing them down to the
stack (Apache CXF already reads them generated DDBeans/descriptor).
This is required for a proper SwitchYard integration into AS7.
Extend WS EndpointPublisher to allow providing properties/metadata
------------------------------------------------------------------
Key: AS7-3324
URL:
https://issues.jboss.org/browse/AS7-3324
Project: Application Server 7
Issue Type: Enhancement
Components: Web Services
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: 7.1.0.Final
The EndpointPublisher spi currently allows for providing @WebService/@WebServiceProvider
annotated endpoint class and deploy endpoint(s) to the running JBoss AS container with an
api pretty much equivalent to the JAXWS Endpoint.publish(..) api. What is missing is the
ability of doing something like:
{code}
List<Source> metadata = new ArrayList<Source>();
StreamSource source = WSDLUtil.getStream(_config.getWsdl());
metadata.add(source);
Map<String, Object> properties = new HashMap<String, Object>();
properties.put(Endpoint.WSDL_SERVICE, portName.getServiceQName());
properties.put(Endpoint.WSDL_PORT, portName.getPortQName());
properties.put(WSDL_LOCATION, WSDLUtil.getURL(_config.getWsdl()).toExternalForm());
...
_endpoint = Endpoint.create(wsProvider); // instance of @WebServiceProvider annotated
class, with no attributes in the annotation
_endpoint.setMetadata(metadata);
_endpoint.setProperties(properties);
_endpoint.publish(publishUrl);
{code}
IOW, we need support for setting properties and metadata and passing them down to the
stack (Apache CXF already reads them from the generated DDBeans/descriptor).
This is required for a proper SwitchYard integration into AS7.
--
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