Transactions are started with the LOCK and commited or aborted by the UNLOCK method and at the corresponding classes you will find support for this. WebdavResource has support too (startTransaction, commitTransaction, ...)
Regards Stefan
Warwick Burrows wrote:
Yes, I guess I mean external transactions in that I want to start and commit transactions from within my application which is a Slide webdav API client. I would like a set of webdav transactions from the webdav API client to slide server to be encapsulated within a transaction so that if any single element fails then the whole transaction is backed out.
So if this is what you mean and your experience has been good then I may try to enable it. Which class implements transaction encapsulation in the webdav client? How would I go about enabling my app to use the webdav client's transaction support?
Thanks, Warwick
-----Original Message-----
From: Stefan L�tzkendorf [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 19, 2004 3:11 AM
To: Slide Users Mailing List
Subject: Re: FW: Stability of transaction support in Slide 2.1b2?
Do mean external transactions?
My recent experiences (with TxFile*Store) are quite good. I plan to rely on it. But of course I'd like to see some more tests in our testsuite(:-)
Stefan
Warwick Burrows wrote:
Guys,
What's are your thoughts on the stability and useability of the transaction support in the WebDAV client? I'd like to hear
of some of
your experiences and whether you believe that the
transaction support
is stable enough to be used. I'm using a JDBC (DB2) nodestore for everything but the content store which is a
TxFileContentStore. I also
noticed that the transaction support jar was updated in
this release
but remember recent mailing lists threads that threw some doubt on whether it was working correctly.
Thanks, Warwick
---------------------------------------------------------------------
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]
-- Stefan L�tzkendorf -- [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
