> Hi,
>
> I'm not familiar with details of a Transactional Manager implementation
and
> particularly a Distributed TM. I have a few questions. What kind of a
> manager is SlideTransactionManager?
It's a TM which is reasonably compliant with JTA and the XA specification.
It implements what Slide needs, and nothing more.
> I remember the answer regarding several parallel transactions. Can Slide
TM
> deal with distributed transactions, particularly with several data sources
> involved in a process like MOVE?
Yes, but it's not a distibuted transaction manager (all the stores are
local).
> I see that all implementations of concrete DataStores are derived from
> XAResource, it is OK, but I see also a lot of extra methods like
> initialize(), reset(), etc. and I wonder which of these methods mandatory
> from the core Slide architecture, considering new implementations of
> specific object-oriented or file-based repositories?
>
> As a sample, I see that during Domain initialization JDBCDescriptorStore
> hits start(), isConnected() many times, not according the number of
possible
> repositories but rather the number of logical child stores( I don't think
> they are supposed to be implemented on different repositories, I 'd rather
> think that the content repository is supposed to be implemented on several
> databases). It somehow bothers me, maybe, I wrong, this is a usual way it
> should work.
isConnected, start and end should be called often, this is normal. However,
start should only be called once for each write operation.
Remy
