> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Dain
> Sundstrom
> Sent: Tuesday, June 26, 2001 2:20 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] High load...
>
>
> > we would have to implement the transaction isolation levels correctly in
> > jboss again I believe that lives at the jbossCMP level. But if we are
> going
> > to support different vendors for the CMP engines we must take this part
> out
> > or at least offer a common API... hmmm must think about it.
> >
>
> I added transaction isolation to the new cmp plugin. You can set it by
> adding the <transaction-isolation> element after the datasource element.
> Valid levels are:
> transaction-none
> transaction-read-committed
> transaction-read-uncommitted
> transaction-repeatable-read
> transaction-serializable
>
> Give me 10 minutes and I'll add it to JAWS...
>
> I don't know if you wanted with user configurable, but for now it
> will allow
> you to play with different levels. I can make it static later.
>
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
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
