> > I guess this is the whole point: current JMS transactional > behaviour > > is fine as long as what you want is *really* to decouple > the producer > > from the consumer, but when what you want is just "transactional > > multithreaded", then it is no more (and by far) a good solution > > because you end up using JMS+MDB for *nothing* > > Exactly! And what you want for multithread transactions is a > cleaner API > that lets you just say 'this method in this class should be run in a > separate thread' and let the server manage the thread pool while you > manage your application code. Get rid of the JMS hullabaloo for this > purpose - it's designed for a different purpose. Also, don't make the > application coders worry about creating a thread, just provide an > aspecty-type thing so that I can plug it all together.
OK then that is the AOP thread interceptor with one-way tags, marcf > > -danch > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: Thawte.com > Understand how to protect your customers personal information > by implementing SSL on your Apache Web Server. Click here to > get our FREE Thawte Apache > Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en > _______________________________________________ > Jboss-development mailing list [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ------------------------------------------------------- This SF.NET email is sponsored by: Thawte.com Understand how to protect your customers personal information by implementing SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
