You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by "Monga, Sunita (GE Healthcare)" <su...@ge.com> on 2013/06/03 22:05:56 UTC
Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF
producer using Payload dataformat
Hello all,
I have a route which sends a request to CXF webservice using Payload dataformat. My question should the response consist of only Soap:body or should it be the entire message soap:envelope
Spring context
<cxf:cxfEndpoint id="xdrReceiverEndpoint"
address="${xdrWebserviceUrl}"
endpointName="s:CcdaXdrServicePort"
serviceName="s:CcdaXdrService"
xmlns:s="http://service.webservices.xdrreceiverimpl.pil.hcit.ge.com">
<cxf:properties>
<entry key="mtom-enabled" value="true"/>
<entry key="dataFormat" value="PAYLOAD"/>
<entry key="loggingFeatureEnabled" value="true"/>
<!-- <entry key="defaultOperationName" value="submitCcda"/>-->
</cxf:properties>
</cxf:cxfEndpoint>
Sample request:
static final String REQ_MESSAGE="<ccdaRequest xmlns=\"" +"http://service.webservices.xdrreceiverimpl.pil.hcit.ge.com/CcdaXdrService\">"
+"<clinicalDocument>"
+"<ccDocument>"
+"<xop:Include xmlns:xop=\"http://www.w3.org/2004/08/xop/include\""
+ " href=\"cid:" + REQ_DOC_CID + "\"/>"
+"</ccDocument>"
+"</clinicalDocument>"
+"</ccdaRequest>";
I am trying to use SoapUI mockservice to mock the response as below
<ccdaResponse xmlns="http://service.webservices.xdrreceiverimpl.pil.hcit.ge.com/CcdaXdrService">
<!--Optional:-->
<ccdaAcknowledgement>
<!--Optional:-->
<statusCode>0</statusCode>
<!--Optional:-->
<statusDesc>Success</statusDesc>
</ccdaAcknowledgement>
</ccdaResponse>
But I get following error
[http-bio-8080-exec-1] WARN org.apache.cxf.phase.PhaseInterceptorChain - Interceptor for {http://service.webservices.xdrreceiverimpl.pil.hcit.ge.com}CcdaXdrService#{http://camel.apache.org/cxf/jaxws/dispatch}Invoke has thrown exception, unwinding now
org.apache.cxf.binding.soap.SoapFault: "http://service.webservices.xdrreceiverimpl.pil.hcit.ge.com/CcdaXdrService", the namespace on the "ccdaResponse" element, is not a valid SOAP version.
at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.readVersion(ReadHeadersInterceptor.java:116)
at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:142)
at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:61)
If the response is the entire soap envelope I get following error. So not sure what the response should like
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(DocLiteralInInterceptor.java:258)
at org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:200)
RE: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF
producer using Payload dataformat
Posted by "Monga, Sunita (GE Healthcare)" <su...@ge.com>.
Thanks Aki for your response.
I think IPF version we use depends on Camel 2.9.2 & CXF 2.6.2, so don’t think we can change the camel version either.
Any way I have it working by specifying the serviceClass. Something to keep in mind in the future when we upgrade I guess.
Thanks so much for your help
Sunita
-----Original Message-----
From: Aki Yoshida [mailto:elakito@gmail.com]
Sent: Thursday, June 06, 2013 10:57 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
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 <el...@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) <su...@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:elakito@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 <wi...@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(Doc
>> > Lit
>> > eralInInterceptor.java:258)
>> > > >
>> > > >
>> > > >
>> > > > at
>> > > >
>> > org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(Do
>> > cLi
>> > 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-tp5733748p
>> > 573
>> > 3881.html
>> > > Sent from the Camel - Users mailing list archive at Nabble.com (
>> > http://Nabble.com).
>> >
>> >
>> >
>> >
>>
>
>
Re: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF
producer using Payload dataformat
Posted by Aki Yoshida <el...@gmail.com>.
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 <el...@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) <su...@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:elakito@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 <wi...@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).
>> >
>> >
>> >
>> >
>>
>
>
Re: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF
producer using Payload dataformat
Posted by Aki Yoshida <el...@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) <su...@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:elakito@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 <wi...@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).
> >
> >
> >
> >
>
RE: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF
producer using Payload dataformat
Posted by "Monga, Sunita (GE Healthcare)" <su...@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:elakito@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 <wi...@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).
>
>
>
>
Re: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF
producer using Payload dataformat
Posted by Aki Yoshida <el...@gmail.com>.
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 <wi...@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/CcdaXdrService}ccdaResponse
> > > found. Expected
> > > {http://camel.apache.org/cxf/jaxws/dispatch}InvokeResponse.
> > >
> > >
> > >
> > > at
> > >
> org.apache.cxf.interceptor.DocLiteralInInterceptor.validatePart(DocLiteralInInterceptor.java:258)
> > >
> > >
> > >
> > > at
> > >
> org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.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-tp5733748p5733881.html
> > Sent from the Camel - Users mailing list archive at Nabble.com (
> http://Nabble.com).
>
>
>
>
Re: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF
producer using Payload dataformat
Posted by Aki Yoshida <el...@gmail.com>.
2013/6/6 Monga, Sunita (GE Healthcare) <su...@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.jiang@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).
>
>
>
>
RE: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF
producer using Payload dataformat
Posted by "Monga, Sunita (GE Healthcare)" <su...@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.
Thanks
Sunita
-----Original Message-----
From: Willem jiang [mailto:willem.jiang@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).
Re: Camel 2.9.2, CXF 2.6.2 - How should the response look for
CXF producer using Payload dataformat
Posted by Willem jiang <wi...@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/CcdaXdrService}ccdaResponse
> > found. Expected
> > {http://camel.apache.org/cxf/jaxws/dispatch}InvokeResponse.
> >
> >
> >
> > at
> > org.apache.cxf.interceptor.DocLiteralInInterceptor.validatePart(DocLiteralInInterceptor.java:258)
> >
> >
> >
> > at
> > org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.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-tp5733748p5733881.html
> Sent from the Camel - Users mailing list archive at Nabble.com (http://Nabble.com).
Re: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF
producer using Payload dataformat
Posted by sunita <su...@ge.com>.
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(DocLiteralInInterceptor.java:258)
>
>
>
> at
> org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.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-tp5733748p5733881.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel 2.9.2, CXF 2.6.2 - How should the response look for
CXF producer using Payload dataformat
Posted by Willem jiang <wi...@gmail.com>.
Hi,
Please don't send the same question into two different users mailing list.
I already answer you question in the cxf users mailing list.
The answer is you the response should be wrapped with soap envelope.
--
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 Tuesday, June 4, 2013 at 4:05 AM, Monga, Sunita (GE Healthcare) wrote:
> Hello all,
>
> I have a route which sends a request to CXF webservice using Payload dataformat. My question should the response consist of only Soap:body or should it be the entire message soap:envelope
>
> Spring context
>
> <cxf:cxfEndpoint id="xdrReceiverEndpoint"
> address="${xdrWebserviceUrl}"
> endpointName="s:CcdaXdrServicePort"
> serviceName="s:CcdaXdrService"
> xmlns:s="http://service.webservices.xdrreceiverimpl.pil.hcit.ge.com">
> <cxf:properties>
> <entry key="mtom-enabled" value="true"/>
> <entry key="dataFormat" value="PAYLOAD"/>
> <entry key="loggingFeatureEnabled" value="true"/>
> <!-- <entry key="defaultOperationName" value="submitCcda"/>-->
> </cxf:properties>
> </cxf:cxfEndpoint>
>
> Sample request:
>
> static final String REQ_MESSAGE="<ccdaRequest xmlns=\"" +"http://service.webservices.xdrreceiverimpl.pil.hcit.ge.com/CcdaXdrService\">"
> +"<clinicalDocument>"
> +"<ccDocument>"
> +"<xop:Include xmlns:xop=\"http://www.w3.org/2004/08/xop/include\""
> + " href=\"cid:" + REQ_DOC_CID + "\"/>"
> +"</ccDocument>"
> +"</clinicalDocument>"
> +"</ccdaRequest>";
>
>
> I am trying to use SoapUI mockservice to mock the response as below
>
>
> <ccdaResponse xmlns="http://service.webservices.xdrreceiverimpl.pil.hcit.ge.com/CcdaXdrService">
> <!--Optional:-->
> <ccdaAcknowledgement>
> <!--Optional:-->
> <statusCode>0</statusCode>
> <!--Optional:-->
> <statusDesc>Success</statusDesc>
> </ccdaAcknowledgement>
> </ccdaResponse>
>
> But I get following error
>
> [http-bio-8080-exec-1] WARN org.apache.cxf.phase.PhaseInterceptorChain - Interceptor for {http://service.webservices.xdrreceiverimpl.pil.hcit.ge.com}CcdaXdrService#{http://camel.apache.org/cxf/jaxws/dispatch}Invoke has thrown exception, unwinding now
> org.apache.cxf.binding.soap.SoapFault: "http://service.webservices.xdrreceiverimpl.pil.hcit.ge.com/CcdaXdrService", the namespace on the "ccdaResponse" element, is not a valid SOAP version.
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.readVersion(ReadHeadersInterceptor.java:116)
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:142)
> at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:61)
>
> If the response is the entire soap envelope I get following error. So not sure what the response should like
>
>
> 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(DocLiteralInInterceptor.java:258)
>
>
>
> at org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:200)