Sunita, not working indeed with cxf-2.6.2 and camel-2.9.2. but it's working with cxf-2.6.2 and camel-2.9.4 (it also works with camel-2.9.3). I previously misquoted the micro version and also got mixed up which one was 4 :-( So this time, I doubled checked the versions. and it is also working with the latest cxf-2.6.x and camel-2.9.x versions, which are cxf-2.6.8 and camel-2.9.7.
so you may consider upgrading at least the camel part if you want to stick to the simple generic dispatcher mode. regards, aki 2013/6/6 Aki Yoshida <elak...@gmail.com> > Sunita, > I seem to have picked the wrong version. > I'll test it again. > regards, aki > > > 2013/6/6 Monga, Sunita (GE Healthcare) <sunita.mo...@ge.com> > >> I am using CXF 2.6.2. We use IPF jars for IHE profile which depend on CXF >> 2.6.2 >> >> >> Did you test with Camel 2.9.2 and CXF 2.6.2 by any chance? >> >> Thanks >> >> Sunita >> >> -----Original Message----- >> From: Aki Yoshida [mailto:elak...@gmail.com] >> Sent: Thursday, June 06, 2013 9:58 AM >> To: users@camel.apache.org >> Subject: Re: Camel 2.9.2, CXF 2.6.2 - How should the response look for >> CXF producer using Payload dataformat >> >> Actually, the payload check by DocLiteranInInterceptor is disabled by >> default for the generic dispatcher mode. >> >> So it is strange. >> >> I thought there could be some version interoperability issue between cxf >> and camel and just ran a test with camel-2.9.2 and cxf-2.6.4. >> but it's working for me. >> >> so it is strange that sunita is getting this error. >> >> >> 2013/6/6 Willem jiang <willem.ji...@gmail.com> >> >> > Hi, >> > >> > I just found you didn't specify the wsdlURL or serviceClass attributes >> > in you CxfEndpoint element. >> > They are useful when CXF is trying to build up ServiceModel for >> > handling the request and response. >> > Can you add either one of them to your CxfEndpoint definition? >> > >> > >> > >> > -- >> > 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/) >> > (English) >> > http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) >> > Twitter: willemjiang >> > Weibo: 姜宁willem >> > >> > >> > >> > >> > >> > On Wednesday, June 5, 2013 at 10:23 PM, sunita wrote: >> > >> > > Hi William, >> > > >> > > Thanks for your response. I was initially posting only on camel user >> > group >> > > but since I did not get any responses to my earlier posts, I decided >> > > to >> > post >> > > on both since it may have different audiences. >> > > >> > > Do you know why I am getting this error when I wrap the response in >> > > soap envelope. I had posted this question earlier as well. >> > > >> > > > org.apache.cxf.interceptor.Fault: Unexpected element { >> > http://model.webservices.ihe.adapters.ccg.dataexchange.hcit.ge.com/Ccd >> > aXdrService}ccdaResponse >> > > > found. Expected >> > > > {http://camel.apache.org/cxf/jaxws/dispatch}InvokeResponse. >> > > > >> > > > >> > > > >> > > > at >> > > > >> > org.apache.cxf.interceptor.DocLiteralInInterceptor.validatePart(DocLit >> > eralInInterceptor.java:258) >> > > > >> > > > >> > > > >> > > > at >> > > > >> > org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLi >> > teralInInterceptor.java:200) >> > > >> > > >> > > >> > > >> > > see the Post with following tittle for more details >> > > >> > > Camel 2.9.2 - Error parsing custom CXF response - >> > > org.apache.cxf.interceptor.Fault: Unexpected element >> > > {http://....CcdaXdrService}ccdaResponse found. Expected >> > > {http://camel.apache.org/cxf/jaxws/dispatch}InvokeResponse >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > -- >> > > View this message in context: >> > http://camel.465427.n5.nabble.com/Camel-2-9-2-CXF-2-6-2-How-should-the >> > -response-look-for-CXF-producer-using-Payload-dataformat-tp5733748p573 >> > 3881.html >> > > Sent from the Camel - Users mailing list archive at Nabble.com ( >> > http://Nabble.com). >> > >> > >> > >> > >> > >
