You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@tomee.apache.org by cocorossello <co...@gmail.com> on 2018/09/13 14:59:05 UTC

Tomee 8 incompatibility

Hi, 

I noticed in latest tomee 8 an incompatibility between versions used in
wss4j and xmlsec (2.0.6)

The stacktrace is:
java.lang.NoSuchMethodError:
org.apache.xml.security.utils.XMLUtils.encodeToString([B)Ljava/lang/String;
       at
org.apache.wss4j.dom.message.token.UsernameToken.addNonce(UsernameToken.java:303)
       at
org.apache.wss4j.dom.message.token.UsernameToken.<init>(UsernameToken.java:264)
       at
org.apache.wss4j.dom.message.WSSecUsernameToken.prepare(WSSecUsernameToken.java:168)
       at
org.apache.wss4j.dom.message.WSSecUsernameToken.build(WSSecUsernameToken.java:225)
       at
org.apache.wss4j.dom.action.UsernameTokenAction.execute(UsernameTokenAction.java:69)
       at
org.apache.wss4j.dom.handler.WSHandler.doSenderAction(WSHandler.java:238)
       at
org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor.access$100(WSS4JOutInterceptor.java:57)
       at
org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor$WSS4JOutInterceptorInternal.handleMessageInternal(WSS4JOutInterceptor.java:275)
       at
org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor$WSS4JOutInterceptorInternal.handleMessage(WSS4JOutInterceptor.java:147)
       at
org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor$WSS4JOutInterceptorInternal.handleMessage(WSS4JOutInterceptor.java:132)
       at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
       at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:537)
       at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:446)
       at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:361)
       at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:319)
       at
org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
       at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:140)

The problem is solved upgrading xmlsec to 2.1.2. I will try to open a PR
with this fix



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html

Re: Tomee 8 incompatibility

Posted by Jonathan Gallimore <jo...@gmail.com>.

Many thanks for sending this over - I've merged it in.

Jon

On Thu, Sep 13, 2018 at 8:01 PM cocorossello <co...@gmail.com> wrote:

> https://github.com/apache/tomee/pull/164
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
>

Re: Tomee 8 incompatibility

Posted by cocorossello <co...@gmail.com>.

https://github.com/apache/tomee/pull/164



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html

Re: Tomee 8 incompatibility

Posted by Jonathan Gallimore <jo...@gmail.com>.

Thanks for the note. I'll look out for the PR and get that merged for you.

Cheers

Jon

On Thu, Sep 13, 2018 at 3:59 PM cocorossello <co...@gmail.com> wrote:

> Hi,
>
> I noticed in latest tomee 8 an incompatibility between versions used in
> wss4j and xmlsec (2.0.6)
>
> The stacktrace is:
> java.lang.NoSuchMethodError:
> org.apache.xml.security.utils.XMLUtils.encodeToString([B)Ljava/lang/String;
>        at
>
> org.apache.wss4j.dom.message.token.UsernameToken.addNonce(UsernameToken.java:303)
>        at
>
> org.apache.wss4j.dom.message.token.UsernameToken.<init>(UsernameToken.java:264)
>        at
>
> org.apache.wss4j.dom.message.WSSecUsernameToken.prepare(WSSecUsernameToken.java:168)
>        at
>
> org.apache.wss4j.dom.message.WSSecUsernameToken.build(WSSecUsernameToken.java:225)
>        at
>
> org.apache.wss4j.dom.action.UsernameTokenAction.execute(UsernameTokenAction.java:69)
>        at
> org.apache.wss4j.dom.handler.WSHandler.doSenderAction(WSHandler.java:238)
>        at
>
> org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor.access$100(WSS4JOutInterceptor.java:57)
>        at
>
> org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor$WSS4JOutInterceptorInternal.handleMessageInternal(WSS4JOutInterceptor.java:275)
>        at
>
> org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor$WSS4JOutInterceptorInternal.handleMessage(WSS4JOutInterceptor.java:147)
>        at
>
> org.apache.cxf.ws.security.wss4j.WSS4JOutInterceptor$WSS4JOutInterceptorInternal.handleMessage(WSS4JOutInterceptor.java:132)
>        at
>
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
>        at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:537)
>        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:446)
>        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:361)
>        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:319)
>        at
> org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
>        at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:140)
>
> The problem is solved upgrading xmlsec to 2.1.2. I will try to open a PR
> with this fix
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
>