Paul
Yes I am using the same idea as the empty service to engage/disengage
modules to support various QOS. Also I discovered a bug in the old code
where the same anonymous service was shared between messages to
engage/disengage - which is sure to cause problems when concurrent
processing occurs with different QOS. Saminda myself and Deepal came up
with a solution based on a proposal by Chamil yesterday to overcome
this, and I will commit the changes as soon as its ready. BTW.. the
empty service is no longer being used.
As Sandesha engaged globally does not mandate service invocations to use
RM, we can easily use RM termination (once the required policy support
is available) without worrying about messages being paused, and how RM
control messages would pass through Synapse etc. Let me writeup on it as
well in parallel to the implementation so that we could test it and
discuss it in detail.
asankha
Paul Fremantle wrote:
Asankha
I'm just working through this and it looks good.
My first comment is that we can also use the existing "empty" model to
support RM and Sec termination and initiation.
We used to do this for addressing. There is an EmptyMessageReceiver,
which does nothing, and then you pass the message through the service
with the required module engaged. This causes the module to act on the
message and then control is returned to the Synapse Mediator chain.
Paul
On 6/7/06, Asankha C. Perera <[EMAIL PROTECTED]> wrote:
I have created a new Wiki page at
http://wiki.apache.org/incubator/Synapse/InProgress/ to link to the
latest documents we are working on at any given time
I have initially described Synapse Proxy services (WSDL mediation) and
how WS-Sec/RM initiation and termination would work here
http://wiki.apache.org/incubator/Synapse/InProgress/Features_and_Design
asankha
---------------------------------------------------------------------
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]
