jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oliver Zeigermann <oliver.zeigerm...@gmail.com>
Subject Re: Jackrabbit Transactions [former: Adding WebDAV to Jackrabbit]
Date Mon, 01 Nov 2004 10:33:41 GMT
Yes, anyone lives in his/her own world. Me as well :)  

Actually Slide has its own JTA implementation! I do not know what
historical even was causing this, but it at least has the benefit that
you do not need a full J2EE server. The drawback was/is that it is
pretty hard to let Slide participate in a distributed transaction of a
J2EE server. As the server side Slide API is suboptimal (hihi) to
program to and it is hard to change the transaction manager the
solution was to create a client side JCA connector talking WebDAV to
Slide that can participate in a JTA transaction of your J2EE server.
This way you have a simply API (client side) to program to as well.

Having said that, maybe it gets a bit easier to understand where I am
coming from. Maybe it even is easier to explain what are the
differences in Jackrabbit.


On Mon, 1 Nov 2004 11:26:16 +0100, David Nuescheler
<david.nuescheler@gmail.com> wrote:
> hi oli,
> just one more thing, now that i was looking at the slide transactions:
> why did you guys implement your own org.apache.slide.transaction.SlideXid, and
> all the other stuff that in my mind belongs into the transaction manager?
> http://jakarta.apache.org/slide/javadoc/org/apache/slide/transaction/SlideXid.html
> did you guys implement your own transaction monitor?
> [experiencing my confusion when looking at the slide tx, i can
> understand your confusion looking at the jackrabbit tx. LOL]
> regards,
> david

View raw message