> > This is the stateless web model. > Not if you have a standalone client. The its should be the stateless RMI > model, or what? > Yes, the RMI proxies are stateless with respect to the client.
> 2. JCA (perhaps) commes in if we raise the question: should current > principal or subject be propagated when opening a JMS connection. > I.e, you obtain a ConnectionFactory in an EJB (through JCA or not), > if you do not use a userid/pwd should the principal/subject be > propagated. Probably yes. > This is a definite yes. > 3. Coordinating JCA and LoginModule, so that they use the same > configuration, or perhaps more correct: for a particular JCA we could > JAAS to use it for autentication. As I said above, this does not > work with the current JBoss code base, at least not in 2.4, but it > is possible to fix (and really nice to use). > The new resource adaptor security will only be implemented in 3.x. The current 2.4 code base does not matter. > Well, a connection hold in vm may possibly be used by different threads, > but the connection should, in case it was started with userid/pwd, hold > ontoit itself, and it ought to be the "server" side that does this. > > Instead of relying on a thread local as in SecurityAssociation and the > security manager (for subject), we could perhaps store the subject in > ClassContextLocal storage. But I am reallt not shure about this now. This will be an implementation detail of your resource adaptor. There will be no use of SecurityAssociation at the resource adaptor level. _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
