DO NOT REPLY [Bug 17786] New: - Call.setProperties() do not seem to make it into the MessageContext

[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=17786>.
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=17786

Call.setProperties() do not seem to make it into the MessageContext

           Summary: Call.setProperties() do not seem to make it into the
                    MessageContext
           Product: Axis
           Version: 1.1rc2
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: Basic Architecture
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: jasnell@us.ibm.com


Properties set on the call object are not making their way into the 
MessageContext.  Example:

If I set the property:

  Call.setProperty("testproperty", "hello world");

And in a handler on the client side request flow call:

  msgContext.getProperty("testproperty");

A null value is returned instead of the expected "hello world"

Attaching a test case that demonstrates the problem