[CXF-173] Support Name Collisions in JAX-WS front end

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-M1
• Fix Version/s: 2.0-M1
• Component/s: JAX-WS Runtime
• Assignee: Willem Jiang
• Reporter: Willem Jiang
• Created: 25/Oct/06 03:59
• Updated: 29/Aug/07 18:01
• Resolved: 26/Oct/06 01:04

Description

WSDL name scoping rules may result in name collisions when mapping from WSDL 1.1 to Java. E.g., a
port type and a service are both mapped to Java classes but WSDL allows both to be given the same name.

Current CXF tool support to resolve this name collisions, but in the service class for client side use ,the service qname is used the changed service name. In this situation , here will throw a .ServiceConstructionException: NO_SUCH_SERVICE when the client start.

For more information , please refer to the Jax-ws 2.0 specification 2.8.1