> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Charles Crain
> Sent: Thursday, September 21, 2000 1:58 PM
> To: jBoss Developer
> Subject: [jBoss-Dev] Transactions and stuff
>
>
> Marc,
>
> Have you guys made headway with the bean-managed transaction problem? I
yes I am coding as we write, BMT and CMT are done, beyond it, it is the
"locking" problems that are mind boggling. I am losing my sanity as it is
hard for me to grock the full big picture. Neither the old impl, neither
the simone stuff offer a full solution and I am growing a bit tired of it
all.
> have been thinking a lot about transactions in general, and trying to
> learn my way around the jBoss transaction code. I think I might have
> come up with a way we can do the following:
>
> - Resolve the conflict between the EnterpriseContext-owned transactions
> and the MethodInvocation-owned transactions
well that is just a fact of life: ctx has a long standing tx and MI can
declare a new one. There is no real "resolving" just "take decision based
on both" (locking for example)
> - Provide UserTransactions to clients within the jBoss VM
done
> - Support distributed transactions between jBoss instances in different
> VM's
great!
> - POSSIBLY provide UserTransactions to out-of-VM clients.
yes that would be good
>
> Of course, this is a pretty huge project, and means some major
> refactoring of the transaction manager. I can't promise any time frame
> on this, but it all needs done, and I will do what I can in the spare
> time I have. I would see it taking 3 weeks at minimum.
>
All I can say is go ahead, send us the "ideas" on how to make it
distributed, I would be delighted to see how you do it.
> One question though, while familiarizing myself with the Tx code, I
> haven't had much time to figure out how the jBoss ClassLoaders work. My
> problem is that to do the above correctly, I'll be adding some stuff to
> jboss-client.jar. The weird thing is, whenever I make ANY changes to
> jboss-client.jar (I am talking additions...I am not taking anything out)
> in the build.xml file, when I boot up jBoss, it all of a sudden can't
> find a bunch of classes. I believe the one it was barfing on
> ServiceMBeanSupport or some such. Do you have any idea why this would
> be? If I manually made a second jar of the classes I needed to expose
> to the client, everything seemed to work fine...it was just messing with
> the build.xml file that seemed to hose everything.
>
This doesn't sound right... build clean/build could solve your problems but
honestly I don't know.
marc
> -Charles
>
>
>
>
