o think that the client side code should not be aware of any need
to call additional mehtods simply to flush a cache, which is an implementation
detail on server side ...
Should we file a bug?
Regards,
abille
View the original post :
http://www.jboss.org/in
Ps. We are using JBoss 5.0.0.GA ...
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215662#4215662
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215662
___
jboss-user mailing
Hello all,
I would be glad to find a solution to the following problem:
I do have a client which will do subsequent calls to login and logout to an EJB
3 server. The principal can be relatively complex. There is a "test" called EJB
- method, which simply returns the name of the callerPrincipal
Hello bhawthorne,
well, we faced the same problem currently and found, that even writing of a own
login module setting the custom principal into the subject does not succeed -
using sessionContext.getCallerPrincipal returns an instance of SimplePrincipal.
This is very annoyning, meaning that th
