Hi,
I think I know what is happening here.
I found the following information associated with the JMS component at the
following link
http://camel.apache.org/jms.html http://camel.apache.org/jms.html
In the section "Message format when sending" it states the following
For the exchange.in.header, the following rules apply for the
header values:
- The values must be primitives or their counter objects
(such as Integer, Long, Character).
The types, String, CharSequence, Date, BigDecimal and
BigInteger are all converted to
their toString() representation. All other types are
dropped.
I believe this is why the token is possibly being dropped. I will look at
the code more closely and see if this is a Camel thing or JMS spec related.
In any case, I would encourage you to log a bug/enhancement request. I will
investigate whether the token can be flattened or type-converted to make it
easier to propagate over ActiveMQ.
Cheers,
Ashwin...
-----
---------------------------------------------------------
Ashwin Karpe
Apache Camel Committer & Sr Principal Consultant
FUSESource (a Progress Software Corporation subsidiary)
http://fusesource.com
Blog: http://opensourceknowledge.blogspot.com
---------------------------------------------------------
--
View this message in context:
http://camel.465427.n5.nabble.com/How-can-Shiro-be-used-with-camel-to-limit-access-to-a-route-tp5521623p5526421.html
Sent from the Camel - Users mailing list archive at Nabble.com.
