Hello,
After a recent change allowing splitting up the broker configuration across
multiple files, starting Artemis fails when the server running broker has no
Internet access. xml:specialAttrs references in artemis-configuration.xsd fail
because the schema location http://www.w3.org/2005/08/xm
What gave you the impression that the "websphere:" Camel transport would
use a message header to determine the target destination rather than using
the value set in the directive? I've never used that transport, so I
can't say for sure that what you're doing is right or wrong, but since it
doesn't
Hi Tim,
I have made a custom processor and trying to add headers to the message before
routing it to the IBM MQ using Camel.
http://camel.apache.org/schema/blueprint";>
