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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Ruwan Linton http://www.wso2.org - "Oxygenating the Web Services Platform"
