synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajith Attapattu" <rajit...@gmail.com>
Subject Re: If the axiom-dom impl is in your classpath synapse seems to have issues.
Date Wed, 11 Jul 2007 13:12:35 GMT
Indika,

Thanks for checking into this.
Let me try to debug more and find out whats going.

Regards,

Rajith

On 7/11/07, indika kumara <indika.kuma@gmail.com> wrote:
>
> hi Rajith
>
> I had tried to reproduce the your issue using the current SVN trunk. I had
> modified the WS-Sec sample number 103 in order to use the xpath
> evaluations together with WS-Sec. The axiom-dom impl also is in the
> classpath. But It is working without an any issue.
>
> The sample configuration
> <definitions xmlns="http://ws.apache.org/ns/synapse ">
>     <localEntry key="sec_policy"
> src="file:repository/conf/sample/resources/policy/policy_3.xml"/>
>     <proxy name="StockQuoteProxy">
>         <target>
>             <inSequence>
>                 <header name="wsse:Security" action="remove"
>                         xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
> "/>
>                 <switch source="//m0:getQuote/m0:request/m0:symbol"
>                         xmlns:m0=" http://services.samples/xsd">
>                     <case regex="MSFT">
>                         <send>
>                             <endpoint>
>                                 <address uri="
> http://bogus:9000/soap/NonExistentStockQuoteService"/>
>                             </endpoint>
>                         </send>
>                     </case>
>                     <case regex="IBM">
>                         <send>
>                             <endpoint>
>                                 <address uri="
> http://localhost:9000/soap/SimpleStockQuoteService"/>
>                             </endpoint>
>                         </send>
>                     </case>
>                     <case regex="SUN">
>                         <send>
>                             <endpoint>
>                                 <address uri="
> http://localhost:9009/soap/NonExistentStockQuoteService"/>
>                             </endpoint>
>                         </send>
>                     </case>
>                 </switch>
>             </inSequence>
>             <outSequence>
>                 <send/>
>             </outSequence>
>         </target>
>         <publishWSDL
> uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
>         <policy key="sec_policy"/>
>         <enableSec/>
>     </proxy>
> </definitions>
>
> thanks
> indika
>
>
> On 7/10/07, Rajith Attapattu <rajith77@gmail.com> wrote:
> >
> > folks,
> >
> > I found the cause for the two problems I highlighted in the list.
> > Both the script mediator and the xpath evaluation (
> > Axis2MessageContext.getStringValue()) had problems dealing with the DOM
> > implementation.
> >
> > Once I removed the axion-dom impl jar from the classpath it went away.
> > Have anybody else experianced this?
> >
> > Has anybody run xpath evaluations or script mediator together with any
> > WS-Sec examples in synapse ?
> > (If I am not mistaken, in WS-Sec u need to have the axiom-dom impl)
> >
> > If this is a problem, shouldn't we fix this? as somebody can technically
> > use the axiom-dom impl instead of the stax impl.
> > (However as Paul stated if we deal at OMElement level it should be ok,
> > but we seem to have some problems with adding or casting nodes in the above
> > two instances)
> >
> > Eran, if the axiom-dom impl is in the classpath (along with stax-impl)
> > which one gets loaded as the OM implementation? does it depend on the Type
> > of factory that u create? Can you explain a bit.
> >
> > Regards,
> >
> > Rajith
> >
> > Regards,
> >
> > Rajith Attapattu
> > Red Hat.
> >
>
>

Mime
View raw message