WebDAV is transactionless. That's right. Though, when you view Slide as a database for content, not only as a WebDAV server, why not having transactions in Slide? Of course a transaction method for external control will be none-WebDAV-standard, but Slide specific.
Oliver
Steve Ebersole wrote:
Thanks for all the info.
Oliver, when you say "a connector to Slide talking WebDAV", are you taking about from inside the XAResource? Isn't WebDAV inherently transactionless?
-----Original Message----- From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] Sent: Thursday, March 04, 2004 3:44 AM To: Slide Users Mailing List Subject: Re: slide and external UserTransactions
Hi Steve,
if you just want to have a transactional file system, plugging in all Slide might be overkill. I have implemented the tx file system to be more or less independent of Slide. Have a look at the classes in org.apache.slide.store.txfile.rm. What you would have to do, though, is to write something like an XAResource suitable to your needs and some notion of a connection to the tx file system. The connection might be a dummy when you only plan to access the local file system.
However, the "clean" way to go would be to have a connector to Slide talking WebDAV. We are currently evaluating this...
As this is a bit off topic, fell free to personally contact me for details.
Cheers, Oliver
Steve Ebersole wrote:
I am interested in proofing usage of Slide as a transactional file store inside some existing apps. The transactional part, however, must be bound to global JTA UserTransactions through external TransactionManager lookups (specifically WebLogic and JBoss TM lookups). I searched the archives and found a message http://marc.theaimsgroup.com/?l=slide-dev&m=105698978309612&w=2 that references a patch to allow Slide to be used in this manner. That message was dated June 6, 2003.
Did that feature make the new 2.0 beta release?
Thanks
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- 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]
