Filter mediator - SOAP1.2

[balaji hari]

When using Synapse filter mediator to check for the presence of 'wsse:Nonce' which will be computed when PasswordDigest is sent, we ran into a situation where the namespace of soap:Envelope / soap:Header need to be given.

This is the entry in config file

<filter xpath="//soap:Envelope/soap:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce"
                xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
            xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
                                 <class name="mil.sddc.websvc.common.synapse.WSTypeCheckMediator">
                                        <property name="wsType" value="RandR"/>
                                </class>
</filter>

In case of SOAP1.2 request, the namcespace mapping fails (namespace for SOAP1.2 being http://www.w3.org/2003/05/soap-envelope) and hence filter mediator returns false.

Is there a way to handle this case (namespaces) independent of SOAP version?

thanks
Balaji

[Ruwan Linton]

Hi Balaji,

Yes this is possible by changing the improving the XPATH expression to handle both soap namespaces. Try the following for the XPATH;

<filter xpath="//soap:Envelope/soap:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce" xmlns:soap=" http://schemas.xmlsoap.org/soap/envelope/"

xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
                                 <class name=" mil.sddc.websvc.common.synapse.WSTypeCheckMediator">
                                        <property name="wsType" value="RandR"/>
                                </class>
</filter>

Thanks,
Ruwan

On 10/3/07, balaji hari <to.haribalaji@...> wrote:

When using Synapse filter mediator to check for the presence of 'wsse:Nonce'
which will be computed when PasswordDigest is sent, we ran into a situation
where the namespace of soap:Envelope / soap:Header need to be given.

This is the entry in config file

<filter
xpath="//soap:Envelope/soap:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce"
                xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"

xmlns:wsse=" http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
                                 <class name="mil.sddc.websvc.common.synapse.WSTypeCheckMediator">
                                        <property name="wsType" value="RandR"/>
                                </class>
</filter>

In case of SOAP1.2 request, the namcespace mapping fails (namespace for
SOAP1.2 being http://www.w3.org/2003/05/soap-envelope ) and hence filter
mediator returns false.

Is there a way to handle this case (namespaces) independent of SOAP version?

thanks
Balaji
--
View this message in context: http://www.nabble.com/Filter-mediator---SOAP1.2-tf4558564.html#a13009181
Sent from the Synapse - Dev mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@...
For additional commands, e-mail: synapse-dev-help@...

--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"

[Ruwan Linton]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Sorry here is the right configuration with XPATH (Accidentally hit the Send before finishing the mail in the earlier case)

<filter
xpath="//s11:Envelope/s11:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce | //s12:Envelope/s12:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce"
                xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/" xmlns:s12="http://www.w3.org/2003/05/soap-envelope "

xmlns:wsse=" http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
                                 <class name="mil.sddc.websvc.common.synapse.WSTypeCheckMediator">
                                        <property name="wsType" value="RandR"/>
                                </class>
</filter>

I hope this will help you to overcome this issue.

Thanks,
Ruwan
 

On 10/3/07, Ruwan Linton <ruwan.linton@...> wrote:

Hi Balaji,

Yes this is possible by changing the improving the XPATH expression to handle both soap namespaces. Try the following for the XPATH;

<filter xpath="//soap:Envelope/soap:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce" xmlns:soap=" http://schemas.xmlsoap.org/soap/envelope/"

xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd ">
                                 <class name=" mil.sddc.websvc.common.synapse.WSTypeCheckMediator">
                                        <property name="wsType" value="RandR"/>
                                </class>
</filter>

Thanks,
Ruwan

On 10/3/07, balaji hari <to.haribalaji@...> wrote:

When using Synapse filter mediator to check for the presence of 'wsse:Nonce'
which will be computed when PasswordDigest is sent, we ran into a situation
where the namespace of soap:Envelope / soap:Header need to be given.

This is the entry in config file

<filter
xpath="//soap:Envelope/soap:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce"
                xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"

xmlns:wsse=" http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
                                 <class name="mil.sddc.websvc.common.synapse.WSTypeCheckMediator">
                                        <property name="wsType" value="RandR"/>
                                </class>
</filter>

In case of SOAP1.2 request, the namcespace mapping fails (namespace for
SOAP1.2 being http://www.w3.org/2003/05/soap-envelope ) and hence filter
mediator returns false.

Is there a way to handle this case (namespaces) independent of SOAP version?

thanks
Balaji
--
View this message in context: http://www.nabble.com/Filter-mediator---SOAP1.2-tf4558564.html#a13009181
Sent from the Synapse - Dev mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@...
For additional commands, e-mail: synapse-dev-help@...

--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"

--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"

[pzfreo]

Neat trick Ruwan. However, I think we should also look at doing some
help inside Synapse to abstract which version of SOAP the message is
in.

Paul

On 10/3/07, Ruwan Linton <ruwan.linton@...> wrote:

> Sorry here is the right configuration with XPATH (Accidentally hit the Send
> before finishing the mail in the earlier case)
>
> <filter
> xpath="//s11:Envelope/s11:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce
> |
> //s12:Envelope/s12:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce"
>
> xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:s12="http://www.w3.org/2003/05/soap-envelope "
>
> xmlns:wsse="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
>                                  <class
> name="mil.sddc.websvc.common.synapse.WSTypeCheckMediator">
>                                         <property
> name="wsType" value="RandR"/>
>                                 </class>
> </filter>
>
> I hope this will help you to overcome this issue.
>
> Thanks,
> Ruwan
>
>
> On 10/3/07, Ruwan Linton <ruwan.linton@...> wrote:
> > Hi Balaji,
> >
> > Yes this is possible by changing the improving the XPATH expression to
> handle both soap namespaces. Try the following for the XPATH;
> >
> > <filter
> xpath="//soap:Envelope/soap:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce"
> xmlns:soap=" http://schemas.xmlsoap.org/soap/envelope/"
> >
> > >
> > >
> xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> ">
> > >                                  <class name="
> mil.sddc.websvc.common.synapse.WSTypeCheckMediator">
> > >                                         <property
> name="wsType" value="RandR"/>
> > >                                 </class>
> > > </filter>
> >
> >
> >
> > Thanks,
> > Ruwan
> >
> >
> >
> >
> >
> > On 10/3/07, balaji hari <to.haribalaji@... > wrote:
> > >
> > > When using Synapse filter mediator to check for the presence of
> 'wsse:Nonce'
> > > which will be computed when PasswordDigest is sent, we ran into a
> situation
> > > where the namespace of soap:Envelope / soap:Header need to be given.
> > >
> > > This is the entry in config file
> > >
> > > <filter
> > >
> xpath="//soap:Envelope/soap:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce"
> > >
> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
> > >
> > > xmlns:wsse="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
> > >                                  <class
> name="mil.sddc.websvc.common.synapse.WSTypeCheckMediator">
> > >                                         <property
> name="wsType" value="RandR"/>
> > >                                 </class>
> > > </filter>
> > >
> > > In case of SOAP1.2 request, the namcespace mapping fails (namespace for
> > > SOAP1.2 being http://www.w3.org/2003/05/soap-envelope )
> and hence filter
> > > mediator returns false.
> > >
> > > Is there a way to handle this case (namespaces) independent of SOAP
> version?
> > >
> > > thanks
> > > Balaji
> > > --
> > > View this message in context:
> http://www.nabble.com/Filter-mediator---SOAP1.2-tf4558564.html#a13009181
> > > Sent from the Synapse - Dev mailing list archive at Nabble.com.
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> synapse-dev-unsubscribe@...
> > > For additional commands, e-mail: synapse-dev-help@...
> > >
> > >
> >
> >
> >
> > --
> > Ruwan Linton
> > http://www.wso2.org - "Oxygenating the Web Services Platform"
>
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"

--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
paul@...

"Oxygenating the Web Service Platform", www.wso2.com

---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@...
For additional commands, e-mail: synapse-dev-help@...

[Ruwan Linton]

Paul,

I don't think that is possible with the current model of the filter, because filter is just doing the filtering depending on the XPATH expression provided. So, it is the users responsibility to give the right XPATH. If synapse is going to be intelligent and do the soap version mapping for the user, he will miss the ability of filtering the soap11 messages over soap12 messages.

Also if we are going to support this then we need to hack in to the XPATH expression provided by the user and change it on the mediator build time to incorporate both soap namespaces. I don't see this as a good solution.

If we can introduce some other mechanism than the XPATH one, then we will be able to support both soap versions, but in that case the expression that the user is providing is not gonna be a standard XPATH. (may be some kind of a regular expression)

WDYT?

Thanks,
Ruwan.

On 10/4/07, Paul Fremantle <pzfreo@...> wrote:

Neat trick Ruwan. However, I think we should also look at doing some
help inside Synapse to abstract which version of SOAP the message is
in.

Paul

On 10/3/07, Ruwan Linton <ruwan.linton@...> wrote:

> Sorry here is the right configuration with XPATH (Accidentally hit the Send
> before finishing the mail in the earlier case)
>
> <filter
> xpath="//s11:Envelope/s11:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce
> |
> //s12:Envelope/s12:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce"
>
> xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/ "
> xmlns:s12="http://www.w3.org/2003/05/soap-envelope "
>
> xmlns:wsse="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
>                                  <class
> name="mil.sddc.websvc.common.synapse.WSTypeCheckMediator">
>                                         <property
> name="wsType" value="RandR"/>
>                                 </class>
> </filter>
>
> I hope this will help you to overcome this issue.
>
> Thanks,
> Ruwan
>
>
> On 10/3/07, Ruwan Linton <ruwan.linton@...> wrote:
> > Hi Balaji,
> >
> > Yes this is possible by changing the improving the XPATH expression to
> handle both soap namespaces. Try the following for the XPATH;
> >
> > <filter
> xpath="//soap:Envelope/soap:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce"
> xmlns:soap=" http://schemas.xmlsoap.org/soap/envelope/"
> >
> > >
> > >
> xmlns:wsse=" http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> ">
> > >                                  <class name="
> mil.sddc.websvc.common.synapse.WSTypeCheckMediator ">
> > >                                         <property
> name="wsType" value="RandR"/>
> > >                                 </class>
> > > </filter>
> >
> >
> >
> > Thanks,
> > Ruwan
> >
> >
> >
> >
> >
> > On 10/3/07, balaji hari <to.haribalaji@... > wrote:
> > >
> > > When using Synapse filter mediator to check for the presence of
> 'wsse:Nonce'
> > > which will be computed when PasswordDigest is sent, we ran into a
> situation
> > > where the namespace of soap:Envelope / soap:Header need to be given.
> > >
> > > This is the entry in config file
> > >
> > > <filter
> > >
> xpath="//soap:Envelope/soap:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce"
> > >
> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/ "
> > >
> > > xmlns:wsse="
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd ">
> > >                                  <class
> name="mil.sddc.websvc.common.synapse.WSTypeCheckMediator">
> > >                                         <property
> name="wsType" value="RandR"/>
> > >                                 </class>
> > > </filter>
> > >
> > > In case of SOAP1.2 request, the namcespace mapping fails (namespace for
> > > SOAP1.2 being http://www.w3.org/2003/05/soap-envelope )
> and hence filter
> > > mediator returns false.
> > >
> > > Is there a way to handle this case (namespaces) independent of SOAP
> version?
> > >
> > > thanks
> > > Balaji
> > > --
> > > View this message in context:
> http://www.nabble.com/Filter-mediator---SOAP1.2-tf4558564.html#a13009181
> > > Sent from the Synapse - Dev mailing list archive at Nabble.com.
> > >
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> synapse-dev-unsubscribe@...
> > > For additional commands, e-mail: synapse-dev-help@...
> > >
> > >
> >
> >
> >
> > --
> > Ruwan Linton
> > http://www.wso2.org - "Oxygenating the Web Services Platform"
>
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"

--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
paul@...

"Oxygenating the Web Service Platform", www.wso2.com

---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@...
For additional commands, e-mail: synapse-dev-help@...

--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"

[asankha]

Paul / Ruwan
> If we can introduce some other mechanism than the XPATH one, then we
> will be able to support both soap versions, but in that case the
> expression that the user is providing is not gonna be a standard
> XPATH. (may be some kind of a regular expression)
We could let the user specify an XPath that applies only to the first
element of the Soap body..(then this will work on either version of
SOAP) or to the envelope itself (i.e. what we have now).. but maybe this
will create un-necessary clutter/confusion?

asankha

---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@...
For additional commands, e-mail: synapse-dev-help@...

[balaji hari]

Thanks for the quick fix. Synapse continues to rock.

Ruwan Linton wrote:

Sorry here is the right configuration with XPATH (Accidentally hit the Send
before finishing the mail in the earlier case)

<filter
xpath="//s11:Envelope/s11:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce
| //s12:Envelope/s12:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce"
                xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:s12="http://www.w3.org/2003/05/soap-envelope"

xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
">
                                 <class name="
mil.sddc.websvc.common.synapse.WSTypeCheckMediator">
                                        <property name="wsType"
value="RandR"/>
                                </class>
</filter>

I hope this will help you to overcome this issue.

Thanks,
Ruwan


On 10/3/07, Ruwan Linton <[e-mail]> wrote:
>
> Hi Balaji,
>
> Yes this is possible by changing the improving the XPATH expression to
> handle both soap namespaces. Try the following for the XPATH;
>
> <filter
> xpath="//soap:Envelope/soap:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce"
> xmlns:soap=" http://schemas.xmlsoap.org/soap/envelope/"
>
> >
> > xmlns:wsse="
> > http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> > ">
> >                                  <class name="
> > mil.sddc.websvc.common.synapse.WSTypeCheckMediator">
> >                                         <property name="wsType"
> > value="RandR"/>
> >                                 </class>
> > </filter>
>
>
>
> Thanks,
> Ruwan
>
>
>
> On 10/3/07, balaji hari <[e-mail] > wrote:
> >
> >
> > When using Synapse filter mediator to check for the presence of
> > 'wsse:Nonce'
> > which will be computed when PasswordDigest is sent, we ran into a
> > situation
> > where the namespace of soap:Envelope / soap:Header need to be given.
> >
> > This is the entry in config file
> >
> > <filter
> > xpath="//soap:Envelope/soap:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce"
> >
> >                 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
> >
> > xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> > ">
> >                                  <class name="
> > mil.sddc.websvc.common.synapse.WSTypeCheckMediator">
> >                                         <property name="wsType"
> > value="RandR"/>
> >                                 </class>
> > </filter>
> >
> > In case of SOAP1.2 request, the namcespace mapping fails (namespace for
> > SOAP1.2 being http://www.w3.org/2003/05/soap-envelope ) and hence filter
> > mediator returns false.
> >
> > Is there a way to handle this case (namespaces) independent of SOAP
> > version?
> >
> > thanks
> > Balaji
> > --
> > View this message in context:
> > http://www.nabble.com/Filter-mediator---SOAP1.2-tf4558564.html#a13009181
> > Sent from the Synapse - Dev mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [e-mail]
> > For additional commands, e-mail: [e-mail]
> >
> >
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"




--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"

[Ruwan Linton]

Hi Balaji,

On 10/4/07, balaji hari <to.haribalaji@...> wrote:

Thanks for the quick fix. Synapse continues to rock.

Thanks & nice to here that.

Ruwan

Ruwan Linton wrote:

>
> Sorry here is the right configuration with XPATH (Accidentally hit the
> Send
> before finishing the mail in the earlier case)
>
> <filter
> xpath="//s11:Envelope/s11:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce
> | //s12:Envelope/s12:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce"
>                 xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/ "
> xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
>
> xmlns:wsse=" http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> ">
>                                  <class name="
> mil.sddc.websvc.common.synapse.WSTypeCheckMediator ">
>                                         <property name="wsType"
> value="RandR"/>
>                                 </class>
> </filter>
>

> I hope this will help you to overcome this issue.

>
> Thanks,
> Ruwan
>
>
> On 10/3/07, Ruwan Linton <ruwan.linton@...> wrote:
>>
>> Hi Balaji,
>>
>> Yes this is possible by changing the improving the XPATH expression to
>> handle both soap namespaces. Try the following for the XPATH;
>>
>> <filter
>> xpath="//soap:Envelope/soap:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce"
>> xmlns:soap=" http://schemas.xmlsoap.org/soap/envelope/ "
>>
>> >
>> > xmlns:wsse="
>> >
>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
>> > ">
>> >                                  <class name="
>> > mil.sddc.websvc.common.synapse.WSTypeCheckMediator">
>> >                                         <property name="wsType"
>> > value="RandR"/>
>> >                                 </class>
>> > </filter>
>>
>>
>>
>> Thanks,
>> Ruwan

>>

>>
>>
>> On 10/3/07, balaji hari <to.haribalaji@... > wrote:
>> >
>> >
>> > When using Synapse filter mediator to check for the presence of
>> > 'wsse:Nonce'
>> > which will be computed when PasswordDigest is sent, we ran into a
>> > situation
>> > where the namespace of soap:Envelope / soap:Header need to be given.
>> >
>> > This is the entry in config file
>> >
>> > <filter
>> >
>> xpath="//soap:Envelope/soap:Header/wsse:Security/wsse:UsernameToken/wsse:Nonce"
>> >
>> >                 xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
>> >
>> >
>> xmlns:wsse=" http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
>> > ">
>> >                                  <class name="
>> > mil.sddc.websvc.common.synapse.WSTypeCheckMediator">
>> >                                         <property name="wsType"
>> > value="RandR"/>

>> >                                 </class>

>> > </filter>
>> >
>> > In case of SOAP1.2 request, the namcespace mapping fails (namespace for
>> > SOAP1.2 being http://www.w3.org/2003/05/soap-envelope ) and hence
>> filter
>> > mediator returns false.
>> >
>> > Is there a way to handle this case (namespaces) independent of SOAP
>> > version?
>> >
>> > thanks
>> > Balaji
>> > --
>> > View this message in context:
>> >
>> http://www.nabble.com/Filter-mediator---SOAP1.2-tf4558564.html#a13009181
>> > Sent from the Synapse - Dev mailing list archive at Nabble.com.
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: synapse-dev-unsubscribe@...
>> > For additional commands, e-mail: synapse-dev-help@...
>> >
>> >
>>
>>
>> --
>> Ruwan Linton
>> http://www.wso2.org - "Oxygenating the Web Services Platform"
>
>
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"
>
>

--
View this message in context: http://www.nabble.com/Filter-mediator---SOAP1.2-tf4558564.html#a13043683
Sent from the Synapse - Dev mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@...
For additional commands, e-mail: synapse-dev-help@...

--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"