Most excellent. That will be very good functionality. In the current code base, am I correct in assuming that using the J2EE store against a container managed datasource will give me XA control via the container's TM? Probably not through WebDAV, but I mean if I use the Slide API?
Basically, I'm thinking that I could utilize the Slide API directly from my application layer (using the above assumption) and have that interaction participate in my global TM transactions. Then the app could serve up WebDAV urls to the clients (browsers via JSP) for further access / manipulation; this part would be transactionless for now, but thats ok. Does that sound kosher? -----Original Message----- From: Daniel Florey [mailto:[EMAIL PROTECTED] Sent: Thursday, March 04, 2004 6:47 AM To: Slide Users Mailing List Subject: Re: slide and external UserTransactions There is an implementation in ms exchange server. But this is not (yet) standard. We will make this feature optional (via slide.properties), so that it will not disturb the webdav compliance if wanted. Daniel [EMAIL PROTECTED] wrote: >Is it in the webdav standard or it is a webdav feature present only in Slide >? >Is it supported into other webdav server ? > >Christophe > > >-----Original Message----- >From: Daniel Florey [mailto:[EMAIL PROTECTED] >Sent: jeudi 4 mars 2004 12:54 >To: Slide Users Mailing List >Subject: Re: slide and external UserTransactions > > >Hi, >we are currently working on a webdav method that will provide some kind >of transaction support via webdav. So this is the basis for >implementing a connector. >regards, >Daniel > >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] > >--------------------------------------------------------------------- >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]
