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.
It seems to me that now I understand the origin of my problems with
CastorJDO integration: ALL underlying Connections should be
non-transactional. Castor-specific XAResourceImpl should be
enlisted in the transaction, Connections are handled indirectly, by
means of Synchronization interface.
Sorry, guys, my bad, the Castor integration was done incorrectly.
Will redo it ASAP.
Best regards,
Oleg
