Hi, Yeah I saw most of those pages but none were particularly satisfactory.
I didn't spend too much time on the solution of publishing to JMS from Camel because I haven't needed to use it in any real environment. Publishing to two different environments certainly throws a spanner in the works for my solution... I avoided any threading changes because I was concerned about its affect on transactions. Ideally you would use a Delegate Processor <http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/processor/DelegateProcessor.html> where you would intercept calls to the JMS endpoint and would override the process method with an implementation that does the privileged action and calls processNext(...). However there's no easy way to do this in Camel (it would be nice to have an intercept(DelegateProcessor) DSL component). You could also take a look at the interceptSendToEndpoint code, and copy/paste a lot of this code such that you can wrap the call to the endpoint process method wrapped in the privileged action; I avoided this because I'm allergic to too much copy/pasting. An ideal solution would be along the lines of: interceptSendToEndpoint("jms:*").delegateProcess(weblogicSecurityProcessor). Cheers, David -- View this message in context: http://camel.465427.n5.nabble.com/Weblogic-JMS-Security-Issues-A-possible-resolution-tp5735108p5735167.html Sent from the Camel - Users mailing list archive at Nabble.com.
