axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 20654] - Java2WSDL gen. duplicate in0 top-level elements of diff types
Date Sun, 13 Jul 2003 03:28:06 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20654>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20654

Java2WSDL gen. duplicate in0 top-level elements of diff types

gdaniels@macromedia.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |axis-dev@ws.apache.org
         AssignedTo|axis-dev@ws.apache.org      |gdaniels@macromedia.com



------- Additional Comments From gdaniels@macromedia.com  2003-07-13 03:28 -------
Confirmed, this is definitely a bug.

This relates somewhat to bug 21519, in that it has to do with the mapping of 
parameters to WSDL and back for document mode.

I think the solution here is probably that the user MUST specify unique 
element names in the WSDD for the service so that we can dispatch on them.  We 
can also do operation dispatch via SOAPAction, but a) that's optional in SOAP 
1.2, and b) we'd still need to avoid emitting duplicate element names with 
different types (if there were two methods with "in0" parameters of different 
Java types).

So for now, I'm planning to implement a true fault (instead of just bad data) 
when emitting duplicate elements in the Emitter.  Beyond that I think we need 
to give examples as to how to make this work.  Again, wrapped mode should 
solve this.

Mime
View raw message