synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ruwan Linton" <>
Subject Re: Synapse as a pure module to engage in to services
Date Mon, 03 Sep 2007 13:11:47 GMT

Assuming this API change is OK to proceed, I have committed the code for the
new handler based mar in the revision r572374.

I have tested this with XSLT, Switch, Validation, Logging, Dropping and all
on the server side. It works just fine but Security and RM are not working
for the moment. Need to test this module on the client side which will be
completely new experiance.

Do we need to support RM and Security with this module?. Any way if we are
to support this both Sandesha2 and Rampart needs to be present under


On 9/2/07, Ruwan Linton <> wrote:
> Hi all,
> Synapse currently gets the message through a SynapseMessageReceiver on the
> Dispatch phase. This will limit the ability for synapse to be engaged in to
> services in axis2. (Synapse wont get the message if there is an actual axis2
> service to which the message gets dispatched)
> Therefore I am working on a new Synapse module which will inject the
> message to synapse using an axis2 handler and after mediation it will let
> the message to flow in the handler chain and invoke the service. In order
> for the dropping message to work in this module we will have to change the
> SynapseEnv API a little bit. That is we need to change the return type of
> the injectMessage method from void to boolean.
> This is because, say we do a validation in Synapse and decided to drop the
> message because the validation fails. In order to inform the handler that it
> needs to return InvocationResponse.ABORT rather than
> InvocationResponse.CONTINUE , injectMessage should say whether to continue
> processing the message in the handler chain or not.
> Comments on this?
> Thanks,
> Ruwan.
> --
> Ruwan Linton
> - "Oxygenating the Web Services Platform"

Ruwan Linton - "Oxygenating the Web Services Platform"

View raw message