On 22 Feb, Scott M Stark wrote: [...] > 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. > >
The current status for JMS is this regarding JCA: the is no support for asynchronous messaging. Ad to this that to use a JCA ra i a non managed environment is a pain in the neck. At least half of the users using JBossMQ does it on a pure/old client-server setup (no J2EE on the client side). This mean that we can not only provide JCA ra for JBossMQ, but must support the vanilla JMS, and thefore managed the secrurity stuff in the all the different IL:s. For the JBoss JMS ra and MDB it might be another matter. We will see. //Peter > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development -- ------------------------------------------------------------ Peter Antman Technology in Media, Box 34105 100 26 Stockholm Systems Architect WWW: http://www.tim.se Email: [EMAIL PROTECTED] WWW: http://www.backsource.org Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942 ------------------------------------------------------------ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
