I have a camel context which has a cxf endpoint to accept messages. The same
camel context has a camel route(route A) which invokes another camel
route(route B).
I executed a small load test (sent 10 request with 3 threads) using soap ui
on the cxf endpoint. The average response time of the camel
Hello,
i have a process with a method signature
public void process(Exchange exchange,@XPath(value=//MyXpath) Object value,
@XPath(value=//MyXpath1)Object value1)
Both the xpath return 1 match when a xml is fed to this processor. I am
expecting the processor to evaluate the xpath and convert to
Thanks arnaudeprez.
This sounds like that this could work.
1. Splitting - i understand , i can unmarshal header and body via xpath
separately and i am good.
Any specific way to collect these two objects and in collection ? And, if i
manage to put my two objects in a collection, in what format
Thanks Matt.
//MyXpath
And the corresponding getter i.e exchange.getProperties().get("bodyPart")
gives me null. Same with Result.
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-pass-multiple-custom-objects-to-processor-tp5754502p57
I have a wsdl with multiple operations and the typical structure of the
message looks like
.
.
..
Can i unmarshal camel context and send MyHeader and MyBody objects to the
processor in proper
Fixed it finally.
I did not intend to use xalan for my transformations however Fuse was being
forced to use this because of one the dependencies in my pom Saxon-HE.
I upgraded to 9.5.1.1, and the maven dependency tree depicted that it no
longer depended on xalan.
I then used ?saxon=ture in my
Bingo!! Exactly what i am facing. .
I am using camel 2.12.
As per the bug definition, this issue is a known issue for Xalan 2.7.1.
Just checked my maven dependency tree, i can see
*xalan:xalan:jar:2.7.0:compile*
net.sf.saxon:Saxon-HE:jar:9.4:compile
[INFO] | +- org.jdom:jdom:jar:1.1:compile
Thanks again Franz.
Debugged a little bit more and it doesnt look like a type conversion issue.
If i pass just tinker with input xml to the xslt, it works in some cases.
More specifically *does not* work and http://mynamespace>
works.
P.S - I am using xsl:copy-of select=*node()|@* in my XS
Thanks for response Franz.
Bean returns an object of javax.xml.transform.Source.
Source s = new DOMSource(myObj)
exchange.getOut().setBody(s);
Thanks
--
View this message in context:
http://camel.465427.n5.nabble.com/XSLT-transformation-produces-junk-charachters-tp5754357p5754366.html
Sent
Hello,
In my camel context, i invoke a java bean (which does some processing) and
returns the body in the exchange. So far so good.
The second log message prints shows the XSLT transformation results in some
junk charachters like and i can see an error in the logs
javax.xml.transform.Tr
10 matches
Mail list logo
