On 6/25/07, Glen Daniels <[EMAIL PROTECTED]> wrote:
David Illsley wrote:
> Yep, properties which are not copied to the operation context in the
> outflow will not be available on the inflow message context (unless
> you walk up the tree and find the related message context).
It might be nice to have a separate API for setting properties in an
OperationContext-accessible way, much as Options automatically makes
them available on the MessageContext.
+1 :-)
Thanks,
Ruchith
Er.. I just noticed that when you set properties on the MessageContext
they actually get set on the Options object?? This behavior has
apparently been there a while - I'm gonna go back and try to find the
threads around it, but this seems stunningly wrong to me(?). I thought
the Options object was one you were supposed to be able to reuse between
calls, where you store the stuff that you, the application (client
usually), care about. Right now it looks like if a Handler sets a "foo"
property on the MC, that property value is going to be persisted across
any invocation using that Options object (and also kept around
unnecessarily if it was a per-MC transient property).... Whaa?
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
www.ruchith.org
www.wso2.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
