Figured it out. I had forgotten the @ sign in the xpath string.
--
View this message in context:
http://camel.465427.n5.nabble.com/Custom-Processor-with-XPath-tp5011728p5014998.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I changed my code to use the NamespaceContext, unfortunately I am still not
getting any matches (tried some simpler strings to test as well). Also, it
seems that adding this bit of code really slowed down the processor, though
it may just be how many times I have deployed / undeployed the bundle a
XPath can be painful to get working. Usually when nothing comes out,
then its a namespace issue.
XPath must have namespaces defined if your XML have namspaces, which
you do not have.
On Tue, Nov 22, 2011 at 5:02 PM, Castyn wrote:
> Good to know. I have the body properly converting to a Documen
Good to know. I have the body properly converting to a Document now.
I suppose this may end up more of an XPath question, so I apologize in
advance but I have looked everywhere for some complicated examples and
haven't had much luck.
Let's say this is the document that is coming into my custom p
Hi
If you use getMandatoryBody then Camel will throw an exception if it
cannot convert to the given type.
On Mon, Nov 21, 2011 at 10:21 PM, Castyn wrote:
> I am attempting to convert a SOAP message from one message format to another,
> and along the way calculating and aggregating data. At any
