You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ax...@ws.apache.org on 2004/10/20 10:31:51 UTC
[jira] Commented: (AXIS-1614) Name collision of generated code caused by AXIS-1598
The following comment has been added to this issue:
Author: Jongjin Choi
Created: Wed, 20 Oct 2004 1:30 AM
Body:
I tested it with all-tests and passed.
The attached patch for ws-axis/java/test/wsdl directory contains required modification for test-cases.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1614?page=comments#action_54379
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1614
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1614
Summary: Name collision of generated code caused by AXIS-1598
Type: Bug
Status: Unassigned
Priority: Major
Project: Axis
Components:
WSDL processing
Versions:
current (nightly)
Assignee:
Reporter: Jongjin Choi
Created: Wed, 20 Oct 2004 1:25 AM
Updated: Wed, 20 Oct 2004 1:30 AM
Description:
After AXIS 1598 was applied, we met a naming problem that did not exist before.
* Problem
WSDL2Java can not process the wsdl which has the same name in portType, operation, complexType and/or other stuff in it.
* Solution
The 4.3.12 of JAX-RPC 1.1 spec addressed this kind of naming collisions. This is partly implemented in current Axis.
The attached patch makes it a little more compliant to JAX-RPC spec.
This also solves the name collision problem of AXIS-1598.
* Caution
In current axis, Axis uses suffixes to resolve the name collision. For xsd:element and wsdl:portType, the suffixes are:
xsd:element -> _ElemType
wsdl:PortType -> _Port
But in JAX-RPC 1.1 spec, the suffixes are:
xsd:element -> _Element
wsdl:PortType -> _PortType
I follow the way of JAX-RPC 1.1 in this patch.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira