[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... ] Gary Brown updated JBIDE-7234: ------------------------------ Environment: JBTools 3.2.0.beta1 nightly build. Description: 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. was: 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. -- 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