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:25:51 UTC
[jira] Created: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
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:25 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
[jira] Commented: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by "Jongjin Choi (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1614?page=comments#action_54783 ]
Jongjin Choi commented on AXIS-1614:
------------------------------------
Dims, Ias.
There is a bug in previous patch.
In Namespaces.java, I put the same namespaces into the pkg2Namespaces vector several times.
The containment check is needed.
The patch will be attached as 'Namespaces.diff.txt'
> Name collision of generated code caused by AXIS-1598
> ----------------------------------------------------
>
> Key: AXIS-1614
> URL: http://issues.apache.org/jira/browse/AXIS-1614
> Project: Axis
> Type: Bug
> Components: WSDL processing
> Versions: current (nightly)
> Reporter: Jongjin Choi
> Assignee: Ias
> Attachments: JavaGeneratorFactory.diff.txt, SamePackageFix.zip, SymbolTable.diff.txt, test.wsdl.diff.txt, wsrf-WS-ResourceProperties-1.2-draft-01-impl.wsdl
>
> 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.
--
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
[jira] Updated: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by ax...@ws.apache.org.
The following issue has been updated:
Updater: Jongjin Choi (mailto:gunsnroz@hotmail.com)
Date: Wed, 20 Oct 2004 1:27 AM
Comment:
a patch of JavaGeneratorFactory.java
Changes:
Attachment changed to JavaGeneratorFactory.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:27 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
[jira] Commented: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by "Ias (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1614?page=comments#action_54798 ]
Ias commented on AXIS-1614:
---------------------------
Applied. Thanks!
> Name collision of generated code caused by AXIS-1598
> ----------------------------------------------------
>
> Key: AXIS-1614
> URL: http://issues.apache.org/jira/browse/AXIS-1614
> Project: Axis
> Type: Bug
> Components: WSDL processing
> Versions: current (nightly)
> Reporter: Jongjin Choi
> Assignee: Ias
> Attachments: JavaGeneratorFactory.diff.txt, SamePackageFix.zip, SymbolTable.diff.txt, test.wsdl.diff.txt, wsrf-WS-ResourceProperties-1.2-draft-01-impl.wsdl
>
> 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.
--
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
[jira] Commented: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Ias
Created: Sun, 24 Oct 2004 10:26 AM
Body:
Unfortunately, JWSDP 1.4's wscompile emits NPE from our impl WSDL.
C:\java\doc\jwstutorial13\examples\jaxrpc\oasis>wscompile -gen config-wsdl.xml -Xprintstacktrace
java.lang.NullPointerException
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processSOAPOperationDocumentLiteralStyle(WSDLModelerBase.java:35
75)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processSOAPOperation(WSDLModelerBase.java:908)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processPort(WSDLModelerBase.java:762)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processService(WSDLModelerBase.java:518)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.internalBuildModel(WSDLModelerBase.java:353)
at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.buildModel(WSDLModelerBase.java:237)
at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelInfo.java:88)
at com.sun.xml.rpc.processor.Processor.runModeler(Processor.java:63)
at com.sun.xml.rpc.tools.wscompile.CompileTool.run(CompileTool.java:714)
at com.sun.xml.rpc.util.ToolBase.run(ToolBase.java:43)
at com.sun.xml.rpc.tools.wscompile.Main.main(Main.java:22)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
error: java.lang.NullPointerException
Meanwhile, I found quite an interesting thing that I had no problem that Jarek and you met regarding packages. My Axis generates correctly test.wsrf.draft package for port types and test.wsrf.draft.xsd package for types (and compiles them OK).
As far as I'm concerned, Sam's point is that AXIS-1598 breaks the backward compatibility against generated artifacts. In other words, you need to (re-)generate artifacts from all your WSDLs and fix your application code using those artifacts to catch up with this "new" Axis.
I think changes from AXIS-1598 and this issue work fine.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1614?page=comments#action_54555
---------------------------------------------------------------------
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: Open
Priority: Major
Project: Axis
Components:
WSDL processing
Versions:
current (nightly)
Assignee: Ias
Reporter: Jongjin Choi
Created: Wed, 20 Oct 2004 1:25 AM
Updated: Sun, 24 Oct 2004 10: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
[jira] Updated: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by 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
[jira] Closed: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by ax...@ws.apache.org.
Message:
The following issue has been closed.
Resolver: Davanum Srinivas
Date: Sun, 24 Oct 2004 12:15 PM
Thanks jongjin. Sam, please check.
-- dims
---------------------------------------------------------------------
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: Closed
Priority: Major
Resolution: FIXED
Project: Axis
Components:
WSDL processing
Versions:
current (nightly)
Assignee: Ias
Reporter: Jongjin Choi
Created: Wed, 20 Oct 2004 1:25 AM
Updated: Sun, 24 Oct 2004 12:15 PM
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
[jira] Updated: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by 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:
Example WSDL (WS-ResourceProperties)
Changes:
Attachment changed to wsrf-WS-ResourceProperties-1.2-draft-01-impl.wsdl
---------------------------------------------------------------------
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
[jira] Commented: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Ias
Created: Wed, 20 Oct 2004 5:42 AM
Body:
Thanks, Jongjin for your so fast response :-)
(We've dealt with the matter so much in the lab really.)
Jarek, Could you test this change with your cases? If it's OK, then it will be soon my turn to make Axis 1.2 have this feature.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1614?page=comments#action_54382
---------------------------------------------------------------------
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: Open
Priority: Major
Project: Axis
Components:
WSDL processing
Versions:
current (nightly)
Assignee: Ias
Reporter: Jongjin Choi
Created: Wed, 20 Oct 2004 1:25 AM
Updated: Wed, 20 Oct 2004 5:42 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
[jira] Commented: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Ias
Created: Sun, 24 Oct 2004 1:09 PM
Body:
Thanks, all who have helped to resolve this issue!
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1614?page=comments#action_54563
---------------------------------------------------------------------
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: Closed
Priority: Major
Resolution: FIXED
Project: Axis
Components:
WSDL processing
Versions:
current (nightly)
Assignee: Ias
Reporter: Jongjin Choi
Created: Wed, 20 Oct 2004 1:25 AM
Updated: Sun, 24 Oct 2004 1:09 PM
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
[jira] Commented: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Davanum Srinivas
Created: Sun, 24 Oct 2004 9:39 AM
Body:
Ias,
does JWSDP exhibit the same problem (IF mapped to the same namespace?)
thanks,
dims
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1614?page=comments#action_54553
---------------------------------------------------------------------
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: Open
Priority: Major
Project: Axis
Components:
WSDL processing
Versions:
current (nightly)
Assignee: Ias
Reporter: Jongjin Choi
Created: Wed, 20 Oct 2004 1:25 AM
Updated: Sun, 24 Oct 2004 9:39 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
[jira] Commented: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Sam Meder
Created: Sun, 24 Oct 2004 8:35 AM
Body:
What's the status of this? It's currently a blocker for us and imo this change should really not happen this late in the release cycle, it will break way too many builds...
/Sam
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1614?page=comments#action_54551
---------------------------------------------------------------------
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: Open
Priority: Major
Project: Axis
Components:
WSDL processing
Versions:
current (nightly)
Assignee: Ias
Reporter: Jongjin Choi
Created: Wed, 20 Oct 2004 1:25 AM
Updated: Sun, 24 Oct 2004 8:35 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
[jira] Commented: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by ax...@ws.apache.org.
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
[jira] Updated: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by ax...@ws.apache.org.
The following issue has been updated:
Updater: Jongjin Choi (mailto:gunsnroz@hotmail.com)
Date: Sun, 24 Oct 2004 10:24 AM
Comment:
Dims,
This is the patch for same package mapping.
The JWSDP will be ok for the case.
There was a bug in previous patch.
Sorry for late response.
I had no spare time to work on it in the meantime.
Changes:
Attachment changed to SamePackageFix.zip
---------------------------------------------------------------------
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: Open
Priority: Major
Project: Axis
Components:
WSDL processing
Versions:
current (nightly)
Assignee: Ias
Reporter: Jongjin Choi
Created: Wed, 20 Oct 2004 1:25 AM
Updated: Sun, 24 Oct 2004 10:24 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
[jira] Commented: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Jongjin Choi
Created: Sun, 24 Oct 2004 10:51 AM
Body:
Dims, Ias, Sam, Jarek.
As a reporter and contributor for AXIS-1614 and AXIS-1598,
I don't insist that they should be included in Axis 1.2 release.
There were much concern for these patches during last week.
You, axis devs, can decide to postpone this pactches until next release.
But I think the Axis guys should be concerned over the jax-rpc 1.1 conformance more than now.
Also in Axis 2.0 release, jax-rpc 2.0 should be considered.
/Jongjin
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1614?page=comments#action_54557
---------------------------------------------------------------------
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: Open
Priority: Major
Project: Axis
Components:
WSDL processing
Versions:
current (nightly)
Assignee: Ias
Reporter: Jongjin Choi
Created: Wed, 20 Oct 2004 1:25 AM
Updated: Sun, 24 Oct 2004 10:51 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
[jira] Commented: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by "Jongjin Choi (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1614?page=comments#action_54784 ]
Jongjin Choi commented on AXIS-1614:
------------------------------------
This is the patch.
cvs diff -u Namespaces.java
Index: Namespaces.java
===================================================================
RCS file: /home/cvspublic/ws-axis/java/src/org/apache/axis/wsdl/toJava/Namespaces.java,v
retrieving revision 1.11
diff -u -r1.11 Namespaces.java
--- Namespaces.java 24 Oct 2004 19:12:56 -0000 1.11
+++ Namespaces.java 29 Oct 2004 05:06:49 -0000
@@ -257,7 +257,10 @@
} else {
v = (Vector)pkg2NamespacesMap.get(value);
}
- v.add(key);
+ // NOT need to add a input key(=namespace value) to v(=package vector);
+ if (!v.contains(key)) {
+ v.add(key);
+ }
pkg2NamespacesMap.put(value, v);
return super.put(key, value);
***** CVS exited normally with code 1 *****
> Name collision of generated code caused by AXIS-1598
> ----------------------------------------------------
>
> Key: AXIS-1614
> URL: http://issues.apache.org/jira/browse/AXIS-1614
> Project: Axis
> Type: Bug
> Components: WSDL processing
> Versions: current (nightly)
> Reporter: Jongjin Choi
> Assignee: Ias
> Attachments: JavaGeneratorFactory.diff.txt, SamePackageFix.zip, SymbolTable.diff.txt, test.wsdl.diff.txt, wsrf-WS-ResourceProperties-1.2-draft-01-impl.wsdl
>
> 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.
--
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
[jira] Commented: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Davanum Srinivas
Created: Wed, 20 Oct 2004 6:53 AM
Body:
Checked in a test case (test/wsdl/wsrf) and your patch...I still see the problem IF http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.wsdl and http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.xsd are both mapped to the same package "test.wsdl.wsrf.draft". you can play with the build.xml in test/wsdl/wsrf to test this.
-- dims
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1614?page=comments#action_54388
---------------------------------------------------------------------
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: Open
Priority: Major
Project: Axis
Components:
WSDL processing
Versions:
current (nightly)
Assignee: Ias
Reporter: Jongjin Choi
Created: Wed, 20 Oct 2004 1:25 AM
Updated: Wed, 20 Oct 2004 6:53 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
[jira] Commented: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Ias
Created: Sun, 24 Oct 2004 9:34 AM
Body:
Probably the actual blocker is AXIS-1598. OK, let's discuss (and vote technically) whether those changes (AXIS-1598 and this issue) should be included in Axis 1.2 (or later like Axis 1.3 or Axis 2).
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1614?page=comments#action_54552
---------------------------------------------------------------------
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: Open
Priority: Major
Project: Axis
Components:
WSDL processing
Versions:
current (nightly)
Assignee: Ias
Reporter: Jongjin Choi
Created: Wed, 20 Oct 2004 1:25 AM
Updated: Sun, 24 Oct 2004 9:34 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
[jira] Commented: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Ias
Created: Sun, 24 Oct 2004 10:32 AM
Body:
Oh, Jongjin also commented but actually I succeeded in testing the case without his SamePacakge patch. (The build script and package settings worked with the current Axis CVS base.)
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1614?page=comments#action_54556
---------------------------------------------------------------------
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: Open
Priority: Major
Project: Axis
Components:
WSDL processing
Versions:
current (nightly)
Assignee: Ias
Reporter: Jongjin Choi
Created: Wed, 20 Oct 2004 1:25 AM
Updated: Sun, 24 Oct 2004 10:32 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
[jira] Updated: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by ax...@ws.apache.org.
The following issue has been updated:
Updater: Jongjin Choi (mailto:gunsnroz@hotmail.com)
Date: Wed, 20 Oct 2004 1:28 AM
Comment:
A patch for ws-axis/java/test/wsdl directory.
Changes:
Attachment changed to test.wsdl.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:28 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
[jira] Commented: (AXIS-1614) Name collision of generated code caused by AXIS-1598
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Jarek Gawor
Created: Wed, 20 Oct 2004 7:30 AM
Body:
Yes, still the same problem. Like Dims mentioned we have both namespaces mapped to the same package.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1614?page=comments#action_54390
---------------------------------------------------------------------
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: Open
Priority: Major
Project: Axis
Components:
WSDL processing
Versions:
current (nightly)
Assignee: Ias
Reporter: Jongjin Choi
Created: Wed, 20 Oct 2004 1:25 AM
Updated: Wed, 20 Oct 2004 7: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