TPC = transaction propagation context.

The dependency on JRMP seems fishy at this time with the IIOP etc invokers.

Would it make sense to keep the in-vm UserTransaction in the tm module but
put a UserTransaction for a given transport mechanism with that invoker? 
Do the different invokers need different client UserTransaction behaviors
or is it just a way to add the tx info to the invocation?

thanks
david jencks

On 2002.05.14 22:39:48 -0400 Jason Dillon wrote:
> Resending due to my messed up sendmail config...
> 
> ----------  Forwarded Message  ----------
> 
> Subject: transaction module & ClientUserTransaction
> Date: Fri, 10 May 2002 11:58:25 -0700
> From: Jason Dillon <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> 
> Who knows about ClientUserTransaction?
> 
> This class is dependent on JRMPInvokerProxy when calling setTPCFatcory 
> on
> construction.  JRMPInvokerProxy has comments about moving this.  I am
> guessing this should be moved to an interceptor, but I am not sure...
> (since
> I don't even know what a TPC is).
> 
> I need this dependency fixed before I can move the tm stuff to its own
>  module.
> 
> Can someone who knows more about this please look into this.
> 
> Thanks,
> 
> --jason
> 
> -------------------------------------------------------
> 
> _______________________________________________________________
> 
> Have big pipes? SourceForge.net is looking for download mirrors. We
> supply
> the hardware. You get the recognition. Email Us:
> [EMAIL PROTECTED]
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
> 
> 

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to