Thanks David. It's crystal clear now.
--
View this message in context:
http://camel.465427.n5.nabble.com/Weblogic-JMS-Security-Issues-A-possible-resolution-tp5735108p5735180.html
Sent from the Camel - Users mailing list archive at Nabble.com.
rtainly an
aspect of over-architecture here with respect to the security model.
Cheers,
David
--
View this message in context:
http://camel.465427.n5.nabble.com/Weblogic-JMS-Security-Issues-A-possible-resolution-tp5735108p5735179.html
Sent from the Camel - Users mailing list archive at Nabble.com.
DMLC is not very configurable here.
- For Outbound JMS: you're intercepting the JMS Producer Endpoint to set the
security context.
--
View this message in context:
http://camel.465427.n5.nabble.com/Weblogic-JMS-Security-Issues-A-possible-resolution-tp5735108p5735175.html
Sent from t
terceptSendToEndpoint("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.
w this message in context:
http://camel.465427.n5.nabble.com/Weblogic-JMS-Security-Issues-A-possible-resolution-tp5735108p5735149.html
Sent from the Camel - Users mailing list archive at Nabble.com.
e in context:
http://camel.465427.n5.nabble.com/Weblogic-JMS-Security-Issues-A-possible-resolution-tp5735108.html
Sent from the Camel - Users mailing list archive at Nabble.com.
