You are correct.
I think Willie Vu was on a similar track: giving the transaction control to the J2EE container.
I've tested this patch with the JBoss transaction manager inside and outside existing transactions (both EJB calls to the SlideAPI and the standard webdav servlet) and also with the built-in transaction manager. Everything seems stable so far (3 days under moderate load). My recommendation for using this patch with EJB and the SlideAPI is to setForceStoreEnlistment(true) for your SlideToken. That way all calls including reads are in the same EJB transaction.
I hope other Slide users can use this patch and post any successes, problems or fixes, and get it all more ready for a Slide commiter.
-Grant
Rob Tomlin wrote:
http://marc.theaimsgroup.com/?l=slide-dev&m=105698978309612&w=2
This was posted to the Slide Developers list yesterday. It appears to take a different approach in that it allows an alternative TM to be used for Slide (correct me if I'm wrong...)
A snip from the post:
========================================================================
Summary:
This patch introduces an new namespace definition parameter which allows you to define an alternate Transaction manager from either a Class or a JNDI lookup.
========================================================================
HTH
Rob
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
