Issue using camel-cxf and wss4j

Hi, When I try to authenticate an HTTP request using WS-Security with camel-cxf & wss4j interceptor, I get the following error : org.apache.camel.spring.Main.main() INFO [org.apache.camel.spring.SpringCamelContext] - Total 1 routes, of which 1 is started. org.apache.camel.spring.Main.main() INFO

Re: Issue using camel-cxf and wss4j

Can you upgrade to wss4j 1.6.9? I had a similar issue... Am 09.01.2013 17:31 schrieb "Charles Moulliard" : > Hi, > > When I try to authenticate an HTTP request using WS-Security with camel-cxf > & wss4j interceptor, I get the following error : > > org.apache.camel.spring.Main.main() INFO > [org.ap

Re: Issue using camel-cxf and wss4j

Will test with 1.6.9. Until now in debug mode, I see that in the class WSS4JInInterceptor, when we handle the message (handleMessage(SoapMessage msg) throws Fault), the element is empty (Element elem = WSSecurityUtil.getSecurityHeader(doc.getSOAPPart(), actor); ) even if a SOAPHeader w

Re: Issue using camel-cxf and wss4j

Get same issue even If I use camel with cxf 2.7.1 and wss4j 1.6.9. Surprisingly the example that we have in camel project (that I created a few years ago) including a unit test succeeds --> https://github.com/apache/camel/blob/trunk/examples/camel-example-reportincident-wssecurity/src/test/java/or

Re: Issue using camel-cxf and wss4j

Find the issue. When we setup camel-cxf endpoint using as DataFormat=MESSAGE, SOAP securityHeaders are removed. On Wed, Jan 9, 2013 at 5:30 PM, Charles Moulliard wrote: > Hi, > > When I try to authenticate an HTTP request using WS-Security with > camel-cxf & wss4j interceptor, I get the followi

Re: Issue using camel-cxf and wss4j

On Thu, Jan 10, 2013 at 12:00 AM, Charles Moulliard wrote: > Find the issue. When we setup camel-cxf endpoint using as > DataFormat=MESSAGE, SOAP securityHeaders are removed. > I think there is a new CXF_MESSAGE or something. There was some new formats added, but never documented. I logged a tick

Re: Issue using camel-cxf and wss4j

In the MESSAGE data format, camel-cxf will not let the interceptor which can build the SOAP message from the input stream to be called. So the WSS4JInInterceptor will not work any more. I think that is why CXF_MESSAGE is introduced, I will dig the code to see if I see the whole picture of it. -

Re: Issue using camel-cxf and wss4j

Different things should be done to improve what we have Why : The warn message which is created by wss4j has nothing to do with the existing problem ? We get this message in the log when we use WS-SECURITTY and camel-cxf with dataFormat=MESSAGE qtp370155726-26 DEBUG [org.apache.cxf.ws.security.w

Re: Issue using camel-cxf and wss4j

I don't find info about this dataFormat (CXF_MESSAGE) in CXF. Does it exist ? On Thu, Jan 10, 2013 at 8:43 AM, Willem jiang wrote: > CXF_MESSAGE -- Charles Moulliard Apache Committer / Sr. Enterprise Architect (RedHat) Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com

Re: Issue using camel-cxf and wss4j

On Thu, Jan 10, 2013 at 10:37 AM, Charles Moulliard wrote: > I don't find info about this dataFormat (CXF_MESSAGE) in CXF. Does it exist > ? Its in camel-cxf, and was recently added to it (eg within the last 6 months or so I think) > > On Thu, Jan 10, 2013 at 8:43 AM, Willem jiang wrote: > >> CX

Re: Issue using camel-cxf and wss4j

That works now with this dataformat=CXF_MESSAGE when using Ws-Security & wss4j. Thx. On Thu, Jan 10, 2013 at 10:45 AM, Claus Ibsen wrote: > On Thu, Jan 10, 2013 at 10:37 AM, Charles Moulliard > wrote: > > I don't find info about this dataFormat (CXF_MESSAGE) in CXF. Does it > exist > > ? > > I

Re: Issue using camel-cxf and wss4j

On Thu, Jan 10, 2013 at 10:53 AM, Charles Moulliard wrote: > That works now with this dataformat=CXF_MESSAGE when using Ws-Security & > wss4j. Thx. > Ah great. Would someone with love for CXF and Camel mind helping with adding docs about these new data formats added to camel-cxf? I dislike when

Re: Issue using camel-cxf and wss4j

I can take care of the document. It looks like we need to do a clean up before release Camel 2.11.0. -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)

Re: Issue using camel-cxf and wss4j

Willem, That could be nice to create in camel cxf page doc a table describing for each DataFormat if we keep or skip headers and what is changed according to CXF interceptors (out and in) ... MESSAGE should be also marked as DEPRECATED now as it is replaces by RAW Regards, Charles On Thu, Jan

Re: Issue using camel-cxf and wss4j

On Jan 10, 2013, at 4:37 AM, Charles Moulliard wrote: > I don't find info about this dataFormat (CXF_MESSAGE) in CXF. Does it exist > ? Yes it exists, but I'm really not exactly happy about how it works. I'd like to kind of "redo" it, but it would require a lot of internal CXF changes which

Re: Issue using camel-cxf and wss4j

On Thu, Jan 10, 2013 at 4:58 PM, Daniel Kulp wrote: > > On Jan 10, 2013, at 4:37 AM, Charles Moulliard wrote: >> I don't find info about this dataFormat (CXF_MESSAGE) in CXF. Does it exist >> ? > > Yes it exists, but I'm really not exactly happy about how it works. I'd > like to kind of "redo"

Re: Issue using camel-cxf and wss4j

On Thu, Jan 10, 2013 at 4:58 PM, Daniel Kulp wrote: > > On Jan 10, 2013, at 4:37 AM, Charles Moulliard wrote: >> I don't find info about this dataFormat (CXF_MESSAGE) in CXF. Does it exist >> ? > > Yes it exists, but I'm really not exactly happy about how it works. I'd > like to kind of "redo"

Re: Issue using camel-cxf and wss4j

+1 for the refactoring of camel-cxf in Camel 3.0. I think we could put the camel-cxf-transport into CXF, as it is mainly used for CXF. And the component just have the dependency of camel-core. For the other cxf-x components we may do some clean up work at the same time. -- Willem Jiang Red H