DO NOT REPLY [Bug 26208] New: - Problem with parsing of body too soon

[bu...@apache.org]

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

Problem with parsing of body too soon

           Summary: Problem with parsing of body too soon
           Product: Axis
           Version: 1.2 Alpha
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: Serialization/Deserialization
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: dug@us.ibm.com


When a global handler asks for the body of the env. it causes the
operations in the msgContext to be set - if that handler changes
the target service then the operations no longer match the ultimate
service invoked.
Attachments will follow:
server-config.wsdd
h.java  (the handler)
rpc1.java rpc2.java msg1.java msg2.java   (sample services)
client.java  (sample client)

as attached client.java should give:
Couldn't find an appropriate operation for XML QName {http://tmp.org}msg1

modify client.java so that the service in the URL doesn't match the
localName of the body.  The handler will use the localName as the service
to change to.  There are four combinations total - I think rpc->rpc is
the only one that works.  Doing things like rpc->msg fails.