2013/6/6 Monga, Sunita (GE Healthcare) <sunita.mo...@ge.com> > Hi William, > > I had tried specifying the wsdlURL but did not work. Not sure if my path > was not wrong. I had put in web-app\wsdl\my.wsdl. Does it need to be under > web-inf? > > Finally I tried generating client classes from the wsdl (using maven code > gen plugin) and specified the serviceClass attribute pointing to the > generated service class. It worked after that. > > Just wondering, are those fields not optional for producer? The request > was going through fine just response handling was failing. > > yeah. actually they are indeed optional for the producer part since 2.8.0. so I replied to the earlier mail by saying it's strange that you are getting this error. and when I ran a test with the same combination of camel and cxf versions, it works fine. So I suspect that you might be picking up another version of camel or cxf that has some interoperability issue.
> Thanks > > Sunita > > -----Original Message----- > From: Willem jiang [mailto:willem.ji...@gmail.com] > Sent: Wednesday, June 05, 2013 10:11 PM > 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 > > 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/ > > > CcdaXdrService}ccdaResponse > > > found. Expected > > > {http://camel.apache.org/cxf/jaxws/dispatch}InvokeResponse. > > > > > > > > > > > > at > > > org.apache.cxf.interceptor.DocLiteralInInterceptor.validatePart(DocL > > > iteralInInterceptor.java:258) > > > > > > > > > > > > at > > > org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(Doc > > > LiteralInInterceptor.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). > > > >
