anonymous wrote : Also, whether you use JAAS or the createConnection with
password, can the consumer of the message know who sent it?
I guess jaikiran is right, it doesn't make sense in JMS to transport the
security context outside of the message. If you want to transport it, you'd
have to enco
Reason why you are getting the exception is :
anonymous wrote : The security methods--getCallerPrincipal() and
isCallerInRole()--also throw a RuntimeException if invoked on a
MessageDrivenContext. When an MDB services a JMS message there is no "caller,"
so there is no security context to be obt
Geert,
Sorry, I do not have the answer but... I am very very interested in it... Have
you made any progress?
Also, whether you use JAAS or the createConnection with password, can the
consumer of the message know who sent it? Typically do you know of any means
to allow an MDB to have the secur
