|Please correct me if I'm wrong(I seem to be wrong about 50% of the
|time :-),
|but, I really don't think you should expose transaction-isolation levels
|within CMP or in the definition of entities. This really belongs in the
|creation of the connection pool. CMP cannot really guarantee that a
|connection will not be shared between different entity types
|within the same
|transaction that use the same connection pool. Actually, I'm pretty sure
which is why I am asking if the jdbc drivers support reconfiguration of the
isolation level on the fly or is it pretty much a "constructor" thingy.
btw if it is the good case (we can change it) then it is not up to minerva
to do this, all minerva does is hand out the connection but it is up to a
functional unit above it, one aware of the application accessing this
connection. That would live in JCA, but it would need to know the
applciation context, or it would purely live in the app server sphere (i.e.
jaws getting the connection, or asking the container to do it on its behalf,
whatever we can do that call somewhere, factored or not).
am i making sense?
marcf
|the minerva connection pool stuff ensures that the same connection
|is shared
|throughout the transaction. Of course, I'm assuming that you're talking
|about configuring the JDBC connection with these new config settings...
|
|Regards,
|
|Bill
|
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
