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 bu...@apache.org on 2003/12/01 03:50:30 UTC

DO NOT REPLY [Bug 19946] - Method namespace problem

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=19946>.
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=19946

Method namespace problem

gdaniels@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From gdaniels@apache.org  2003-12-01 02:50 -------
Upon a closer look, the examples aren't identical.  In the first case you have 
the method element qualified and the argument accessors unqualified, which is 
correct according to SOAP 1.1 RPC.  In the second case the default namespace 
has been set on the method element, and therefore the argument accessors are 
namespace qualified, which is very different.

I'm marking this INVALID for right now - if you can show that Axis is messing 
up here somehow (incorrectly processing WSDLs to generate bad XML or 
something), please feel free to reopen the bug and include a specific 
example.  Thanks!