Title: Backend session information - Tx - Data distribution

Hi,

I already asked this question on the user-list, but got not a single answer. Could somebody help me please?

I want to create something which keeps track of some backend session information, for data distribution purposes to offline clients.

In that session-info are things like the user logged in, data sharing information (some distribution of data is use case specific, most are DB based though), etc.  It is important that data is distributed only when the container transaction commits.

What's the best way to do this?

Create an MBean, just like the TxManager works, with a ThreadLocal variable?
What will happen with the transaction information of that current thread (ThreadInfo inside the TxManager) in this case?

Also, is it possible to lookup the current transaction or transactionID or info or transaction information?


Thanks in advance for any tips!

Wonne

Reply via email to