One quick update, I replace cxf producer end point with http4 component and
the route ran with no issues/problems.
However I still would like to understand why cxf end point is failing.
Thanks,
Pravin
--
View this message in context:
My route is very similar to the route what is being discussed on this thread
and I too am facing same issues. I have tried all the options suggested,
however nothing works.
Did anyone fixed this problem in their route. Appreciate any inputs.
Thanks,
Pravin
--
View this message in context:
After XSLT transformation try converting to "org.w3c.dom.Document".
--
View this message in context:
http://camel.465427.n5.nabble.com/please-help-with-transformation-of-a-response-by-xslt-tp5756711p577.html
Sent from the Camel - Users mailing list archive at Nabble.com.
thanks, run the transformation to String after the XSLT transformation,
continuous error, I think it's my transformation which is having problems,
I'll check, thank you very much for your help
--
View this message in context:
Thank you very much for this information, and check the coding of the
original RESPONSE and matches my XSLT transformation, both are UTF-8.
--
View this message in context:
http://camel.465427.n5.nabble.com/please-help-with-transformation-of-a-response-by-xslt-tp5756711p5756852.html
Sent from
effectively, since last week Always change a PAYLOAD to MESSAGE data format.
I'm about to check out the transformation with the manager of that part
because apparently that's where we're having problems, thank you very much
--
View this message in context:
Hi,
Just some comments about the convert to string workaround for XML documents.
Though XML documents may look like strings, they are in fact binary data, so
even if converting the data to string may help to work around an existing
issue, it can cause other issues with specific XML documents.
Do the conversion after:
to uri=xslt:xslt/ClubPremier/response.xslt /
convertBodyTo type=java.lang.String /
Henrique Viecili
On 20 September 2014 00:00, aioria3077 aioria3...@gmail.com wrote:
*thanks for replying, really like right before calling xsl transformer, I
have this
if the call to the original web service, the change will dataFormat MESSAGE
by PAYLOAD, The error is:
The PayLoad elements cannot fit with the message parts of the
BindingOperation. Please check the BindingOperation and PayLoadMessage.
I make the first transformation successfully receiving
If you invoke the backend service with PAYLOAD data formate message you need to
setup the BindingOperation for it.
My suggestion if you want to use xslt to the transformation, you can just use
MESSAGE data formate to invoke the back end service.
--
Willem Jiang
Red Hat, Inc.
Web:
After the xsl transformation, try to convert the body again to String.
Henrique Viecili
On 19 September 2014 10:16, aioria3077 aioria3...@gmail.com wrote:
*have a original Web Services, a proxy which has a transformation because
you
need to add data authentication, the request works fine,
*thanks for replying, really like right before calling xsl transformer, I
have this line*
* convertBodyTo type=java.lang.String /*
to uri=xslt:xslt/ClubPremier/response.xslt /
will try to put it back then see what happens.
any other suggestions?
--
View this message in
*have a original Web Services, a proxy which has a transformation because you
need to add data authentication, the request works fine, can consume the
service, but I need to transform the response to the expectations created my
webService proxy, the transformation applied in the same way which the
13 matches
Mail list logo
