Tijs I figured out what's going on. Although our MessageContext is a mapping onto the underlying Axis2 MC, we have our own properties too. So when we set-property, that doesn't get reflected in the underlying Axis2 MC, so it doesn't affect Sandesha2.
Three simple options I can see: 1) get rid of our properties and just have the axis2 mc properties.. If a user wants to avoid overwriting an underlying axis2 property, just make sure this has a unique name. I don't think we actually use this feature but maybe I'm wrong. 2) add a set-axis2-property which modifies the underlying axis2 property. 3) add a specific lastmessage mediator. Thoughts everyone? Paul On 12/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Paul, Has there been some progression with the WS-Reliable Messaging last message for the termination of the sequence? Thanks, Tijs Tijs You are quite right. The set-property isn't working. I'm just debugging it. The property should be going right through to the sandesha module which is why you can't find the code in Synapse. Paul On 12/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Paul, > > I have tried to use the set-property element, but I don't see any change in the WS-RM handling. > Where exactly does the set-property needs to be set in the Synapse flow configuration file? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
