You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "willem Jiang (JIRA)" <ji...@apache.org> on 2006/10/25 07:46:17 UTC
[jira] Updated: (CXF-173) Support Name Collisions in JAX-WS front
end
[ http://issues.apache.org/jira/browse/CXF-173?page=all ]
willem Jiang updated CXF-173:
-----------------------------
Issue Type: Bug (was: New Feature)
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
was:
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 the runtime build service modle from wsdl can support this.
So we need to add an JAX-WS Service modle in the Jax-ws front end to sovle this name collisions.
For more information , please refer to the Jax-ws 2.0 specification 2.8.1
> Support Name Collisions in JAX-WS front end
> --------------------------------------------
>
> Key: CXF-173
> URL: http://issues.apache.org/jira/browse/CXF-173
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.0-M1
> Reporter: willem Jiang
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira