You could also you JMS with XA - send messages out containing whatever you need to track. This will be sent iff the transaction commits. You can then write an MDB (or any other listener) to take the messages and do whatever you want with them. You actually could (maybe) make the offline clients registered listeners on the topic(s) - that way when they connect they should get all of the messages sent since their last connect.
JMS experts, correct me if I'm out of line, here. -danch David Jencks wrote: > I'm still a little unclear about what you want. I think it is to be > notified right after every transaction commits. Unfortuneately there is no > way to register a listener with the tx manager for all transactions. > > I think the simplest ways to do this are: > if you use only cmt, no bmt, modify the tx interceptor to call something > after (successful) commit > > If you use bmt as well, modify the tx manager to notify you. > > david jencks > > On 2002.06.06 02:29:52 -0400 "Keysers, Wonne" wrote: > >>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 >> >> >><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> >><HTML> >><HEAD> >><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII"> >><META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.19"> >><TITLE>Backend session information - Tx - Data distribution</TITLE> >></HEAD> >><BODY> >> >><P><FONT SIZE=2>Hi, </FONT> >></P> >> >><P><FONT SIZE=2>I already asked this question on the user-list, but got >>not a single answer. Could somebody help me please?</FONT> >></P> >> >><P><FONT SIZE=2>I want to create something which keeps track of some >>backend session information, for data distribution purposes to offline >>clients.</FONT></P> >> >><P><FONT SIZE=2>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.</FONT></P> >> >><P><FONT SIZE=2>What's the best way to do this?</FONT> >></P> >> >><P><FONT SIZE=2>Create an MBean, just like the TxManager works, with a >>ThreadLocal variable? </FONT> >><BR><FONT SIZE=2>What will happen with the transaction information of >>that current thread (ThreadInfo inside the TxManager) in this case? >></FONT></P> >> >><P><FONT SIZE=2>Also, is it possible to lookup the current transaction or >>transactionID or info or transaction information?</FONT> >></P> >><BR> >> >><P><FONT SIZE=2>Thanks in advance for any tips!</FONT> >></P> >> >><P><FONT SIZE=2>Wonne</FONT> >></P> >> >></BODY> >></HTML> >> > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
