On Monday, December 9, 2002, at 10:51 AM, David Ward wrote:
Only one thread is allowed to be associated with a transaction at a time (it's in one of the specs), so which spawned thread gets the tx?Bill Burke wrote:Answer?
Because there is no way to propagate transaction and security contexts to
the spawned threads unless J2EE provided a thread creation API.
Bill
I was under the impression that transaction and security context propagation was done using java.lang.ThreadLocal - a nice way to have a variable available to all work done in a server request thread (without having to pass the same params to everyone), as long as the class holding the (ThreadLocal) variable lives in a common > ClassLoader.
Now, to address accessing it via spawned threads, wouldn't java.lang.InhertiableThreadLocal work for tx and sx propagation? Take a look at the class description in javadoc.
The real problem I see is orchestrating a single, safe commit... when?
-dain
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
