Resume and suspend are used to resume and suspend the "Transaction" as in
"suspend this transaction".
We need to resume and suspend the association of the Thread to the
transaction (under JOnAS this was clear, they knew transactions, it was
getPropagationContext and setPropagationContext).
marc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Rickard �berg
> Sent: Tuesday, August 01, 2000 12:51 PM
> To: jBoss Developer
> Subject: Re: [jBoss-Dev] rmi,transactions,orbs [was: TransactionImpl]
>
>
> Yo
>
> marc fleury wrote:
> > I think I kinda see the need for a non-distributed
> implementation of full
> > JTA and needed TS. It would need to be pluggable just like the other
> > "services" to the container right now.
>
> Alright.
>
> > If we do non distributed we can make a fast stand alone server. I mean
> > people don't really use web transactions that well right now,
> and so first
> > they need to learn them, and then we might see a need to
> actually distribute
> > the transaction (and do all the fancy Propagation of Context she refers
> > too).
> >
> > In short, writing that simple interface for pluggability, (we need the
> > thread association methods and no they are not resume and suspend ;-) is
> > trivial.
>
> Hm.. why are they not resume and suspend? I got the impression from
> reading the Javadocs of javax.transaction.TransactionManager that this
> is indeed the purpose of those two methods. What have I missed? What are
> they used for then?
>
> /Rickard
>
> --
> Rickard �berg
>
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
>
