Oleg Nitz wrote:
ON> Oleg Nitz wrote:
DO>>> You could then declaratively express in a server configuration
DO>>> file the transaction characteristics of the resources
DO>>> that you retrieve: enlisted in the transaction or not.
ON>> Declaratively? I guess it would be defined dynamically: for CastorJDO
ON>> all Connections except for KeyGenerator's ones should be enlisted in
ON>> the transaction.
ON> It seems to me that now I understand the origin of my problems with
ON> CastorJDO integration: ALL underlying Connections should be
ON> non-transactional. Castor-specific XAResourceImpl should be
ON> enlisted in the transaction, Connections are handled indirectly, by
ON> means of Synchronization interface.
ON> Sorry, guys, my bad, the Castor integration was done incorrectly.
ON> Will redo it ASAP.
I was panic-stricken, just a little fix to Castor was needed.
All Connections are now enlisted in the transaction, HIGH/LOW key
generator now can use the same transactional Connection
("same-connection" parameter of HIGH/LOW key generator must be set to
"true") and holds lock on the "sequence table" until the end of the
transaction (for now it is the best way).
All is fine, CastorJDO happily plays with Minerva
XADataSourceLoader!!! :-)
Now committing to CVS...
Best regards,
Oleg
