Dan OConnor wrote:
DO> Obviously an MBean is different from a persistence manager, but we
DO> might want to adopt this standard for MBeans as well.
I believe that CastorJDO is a kind of persistence manager by nature.

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.
Declaratively? I guess it would be defined dynamically: for CastorJDO
all Connections except for KeyGenerator's ones should be enlisted in
the transaction.
How about the following: to bind two DataSources for each database URL
to different JNDI names, one for transactional Connections, another
for non-transactional ones.

DO> P.S.  I'll try to read your e-mails before responding to them from 
DO> now on!
I'll try to produce shorter e-mails :-)

Best regards,
 Oleg 



Reply via email to