We are developing a store, that support multiple transactions. As Remy
mentioned all depends on the child stores. If your child stores can inherit
from a XA resource manager (for example you are using a SQL system, which
supports 2 phase commit) that is basically everything you need to do.
If your physical storage system does not support XA Resouce, you will need
to implement this in your child store. Basically your child stores could
inherit form org.apache.slide.common.AbstractService, but you would still
need to overwrite some/most of the XA methods to be able to drive your
storage system correctly (e.g. prepare/commit, abort, ...). Your storage
connections could be stored in a hash table with the key of the current
thread name (the is what we do at least).
Hope this helped you a bit.
Best regards
Juergen Pill
-----Original Message-----
From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
Sent: Saturday, May 05, 2001 9:05 AM
To: [EMAIL PROTECTED]
Subject: Re: multiple transactions
> Hi....
> It looks like slide has support for multiple transactions.
> Can someone explain to me why it cannot do more than 1
> write operation at the same time? Is it a bug or feature?
It's a feature caused by the limitations of the stores (which for all
transaction purposes act as XA resource managers).
Basically, they won't allow to be enlisted in more than one transaction.
MOre advanced stores will be developped eventually, and won't have those
limitations (for example, a JDBC store which would use a XADataSource).
It's all about what can (or cannot) do the backend ...
Remy
