[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-7234) JAX-WS generated portType implementation has incorrect @WebService annotation
[
https://jira.jboss.org/browse/JBIDE-7234?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick updated JBIDE-7234:
-------------------------------------
Fix Version/s: 3.2.0.Beta2
Ok, as there seems to be a workaround, I'm going to push this to the Beta2 release.
Can I summarize that somehow you want the implementation class annotations to include the
serviceName attribute and set the endpointInterface?
So in this case:
serviceName="CreditAgencyService"
endpointInterface =
"org.example.purchasing.creditAgency.CreditAgencyInterface"
The endpointInterface is just the fully qualified class name of the interface class, so
that should be easy to include. But for the serviceName, we may have to add a separate
field to the JBoss Web Service Code Generation Configuration page of the wizard that
currently asks for the Package name, specification level, etc. If we add a "Service
name" field we might be able to come up with a suitable default for it...
Lukas, any idea how we'd query the WSDL to get the service name before we start the
whole JBossWS generation process?
JAX-WS generated portType implementation has incorrect @WebService
annotation
-----------------------------------------------------------------------------
Key: JBIDE-7234
URL: https://jira.jboss.org/browse/JBIDE-7234
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.2.0.M2
Environment: JBTools 3.2.0.beta1 nightly build.
Reporter: Gary Brown
Assignee: Brian Fitzpatrick
Fix For: 3.2.0.Beta2
Attachments: PurchaseGoodsProcess-CreditAgency.zip
When generating a Java Bean skeleton web service, based on a WSDL definition, the port
type implementation class has an incorrect annotation.
The port type implementation has:
@WebService(serviceName = "CreditAgencyInterface", endpointInterface =
"org.example.purchasing.creditAgency.CreditAgencyInterface")
but the interface associated with the implementation defines:
@WebService(name = "CreditAgencyInterface", targetNamespace =
"http://www.jboss.org/examples/creditAgency")
The end result is that when accessing the WSDL for the endpoint, once deployed to the
JBossAS server, the WSDL has an incorrect target namespace and service name - service name
is 'CreditAgencyInterface' instead of 'CreditAgencyService', and the
target namespace is autogenerated based on the Java package name of the implementation
class.
When the annotation in the port type implementation's annotation was changed to be:
@WebService(name = "CreditAgencyInterface",
serviceName="CreditAgencyService",
targetNamespace="http://www.jboss.org/examples/creditAgency";, endpointInterface
= "org.example.purchasing.creditAgency.CreditAgencyInterface")
This fixes the serviceName attribute, and adds a 'name' attribute to be the port
type. It also specifies explicitly the target namespace.
Note: tried using jax-ws version 2.0 and 2.1, with same result.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira