Marc,
Have you guys made headway with the bean-managed transaction problem? I
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
- Provide UserTransactions to clients within the jBoss VM
- Support distributed transactions between jBoss instances in different
VM's
- POSSIBLY provide UserTransactions to out-of-VM clients.
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.
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.
-Charles
