You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by L F <l8...@yahoo.com.INVALID> on 2015/01/16 23:58:11 UTC
Camel + CXF + XSL Exception when creating the Soap response
Hello camel users !
I'm trying to implement a webservice as a camel route, defined using blueprint.
I have the message as XML but after i create the response, CXF is not sending it back as it should.
If i use dataFormar PAYLOAD, i get "The PayLoad elements cannot fit with the message parts of the BindingOperation. Please check the BindingOperation and PayLoadMessage." exception,If i use dataFormat=MESSAGE i get "URI is not absolute" exception.
I'm probably doing something wrong, but i'm unable to find out the problem, so any help is appreciated.
Thanks!
Re: Camel + CXF + XSL Exception when creating the Soap response
Posted by L F <l8...@yahoo.com.INVALID>.
Hello Aki,
By removing the <to uri="cxf:bean:..." /> step, i have a response in SoapUI. Thank you for help, i would never find out what is the problem,
Regards Laji
On Monday, January 19, 2015 3:51 PM, Aki Yoshida <el...@gmail.com> wrote:
the error that you get for the PAYLOAD type means your response
message doesn't match the response message defined in your wsdl. So,
you will need to verify this.
the error that you get for the MESSAGE type is caused by your
misconfiguration in your blueprint.xml. You cannot have <to
uri="cxf:bean:..." /> to return a response message to that endpoint.
If you need to return a response to the original call, you need to
just leave the response message in the route so that it will be
returned to that from endpoint. The to endpoint in CXF is used to send
a request message (and possibly to put its response message back in
the route). I suppose, you are getting the "URI is not absolute" error
because this endpoint's url is not absolute.
regards, aki
2015-01-16 23:58 GMT+01:00 L F <l8...@yahoo.com.invalid>:
> Hello camel users !
>
> I'm trying to implement a webservice as a camel route, defined using
> blueprint.
>
> I have the message as XML but after i create the response, CXF is not
> sending it back as it should.
>
> If i use dataFormar PAYLOAD, i get "The PayLoad elements cannot fit with the
> message parts of the BindingOperation. Please check the BindingOperation and
> PayLoadMessage." exception,
> If i use dataFormat=MESSAGE i get "URI is not absolute" exception.
>
> I'm probably doing something wrong, but i'm unable to find out the problem,
> so any help is appreciated.
>
> Thanks!
>
>
Re: Camel + CXF + XSL Exception when creating the Soap response
Posted by Aki Yoshida <el...@gmail.com>.
the error that you get for the PAYLOAD type means your response
message doesn't match the response message defined in your wsdl. So,
you will need to verify this.
the error that you get for the MESSAGE type is caused by your
misconfiguration in your blueprint.xml. You cannot have <to
uri="cxf:bean:..." /> to return a response message to that endpoint.
If you need to return a response to the original call, you need to
just leave the response message in the route so that it will be
returned to that from endpoint. The to endpoint in CXF is used to send
a request message (and possibly to put its response message back in
the route). I suppose, you are getting the "URI is not absolute" error
because this endpoint's url is not absolute.
regards, aki
2015-01-16 23:58 GMT+01:00 L F <l8...@yahoo.com.invalid>:
> Hello camel users !
>
> I'm trying to implement a webservice as a camel route, defined using
> blueprint.
>
> I have the message as XML but after i create the response, CXF is not
> sending it back as it should.
>
> If i use dataFormar PAYLOAD, i get "The PayLoad elements cannot fit with the
> message parts of the BindingOperation. Please check the BindingOperation and
> PayLoadMessage." exception,
> If i use dataFormat=MESSAGE i get "URI is not absolute" exception.
>
> I'm probably doing something wrong, but i'm unable to find out the problem,
> so any help is appreciated.
>
> Thanks!
>
>