Hi Asankha (and others), The code that you committed works fine. I saw changed the correlate property. I did not understand this functionality from the set-proptery specification that you made, but it seems to be working fine.
I think option 1 is a too much depending on specific values of the name and value attributes of the set-property. Therefore I would like to go for a RMSequence mediator. Anybody who thinks this is not the way to go? Thanks, Tijs -----Oorspronkelijk bericht----- Van: Asankha C. Perera [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 19 december 2006 12:44 Aan: [email protected] Onderwerp: Re: Feedback on starting sequence Hi Tijs I prefer to use option #1 if it works, as it would re-use the existing code we have already. If you prefer #2, I would suggest to use <RMSequence action="begin|end"/> instead of introducing two mediators. BTW, I was unable to test the code I committed for synapse-47, could you please check it as I made a few changes to your original patch. thanks asankha [EMAIL PROTECTED] wrote: > Hi all, > > To include the starting of sequences into Synapse, I would like some feedback on how to develop this into the Synapse code. Can you please give some feedback on this? > To be able to start a sequence whenever you want to, we have to add something to the Synapse configuration. Because the default behaviour of the Sandesha2 implementation is that a message send to the same endpoint is automatically part of the same sequence. Therefore we need to explicitly set the sequence identifier ourselves to identify the beginning of a new sequence. We can use the UUIDGenerator.getUUID() axis2 method for this. But how are we going to incorporate this into the Synapse configuration? I can think of the following options: > > option 1: <set-property name="SandeshaRM" value="startsequence" scope="axis2"/> > option 2: <startRMSequence/>, but then we should also have an <endRMSequence/> I think. > > Can you think of other (better) options or do you have a preference for an option? > > Thanks > > Tijs > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
