[jira] Updated: (AXIS-1614) Name collision of generated code caused by AXIS-1598

[ax...@ws.apache.org]

The following issue has been updated:

    Updater: Jongjin Choi (mailto:gunsnroz@hotmail.com)
       Date: Wed, 20 Oct 2004 1:26 AM
    Comment:
a patch for SymbolTable.java
    Changes:
             Attachment changed to SymbolTable.diff.txt
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/AXIS-1614?page=history

---------------------------------------------------------------------
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:26 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