[jbossws-issues] [JBoss JIRA] (JBWS-3798) @WebEndpoint name not considered when building up webservicerefs
Alessio Soldano (JIRA)
issues at jboss.org
Wed Aug 27 13:28:59 EDT 2014
[ https://issues.jboss.org/browse/JBWS-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alessio Soldano updated JBWS-3798:
----------------------------------
Fix Version/s: jbossws-cxf-4.3.1
> @WebEndpoint name not considered when building up webservicerefs
> ----------------------------------------------------------------
>
> Key: JBWS-3798
> URL: https://issues.jboss.org/browse/JBWS-3798
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-4.3.1, jbossws-cxf-5.0
>
>
> When building up webservice refs for a provided Service class, we currently look for 'getXYZ' methods with proper return type and select the first one with proper signature (for instance supporting WebServiceFeature).
> A user provided Service class could possibly have multiple getPortName methods returning the same service endpoint interface, but actually using different wsdl ports. That is possible when different @WebEndpoint annotations are specified. In such a scenario, if the user has also specified the required port QName in the webserviceref metadata (port-component-ref block, for instance in jboss-web.xml), we need to select the right method my matching the name of the @WebEndpoint annotation.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
More information about the jbossws-issues
mailing list