> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Dain
> Sundstrom
> Sent: Wednesday, June 27, 2001 11:43 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] CVS update:
> jboss/src/main/org/jboss/ejb/plugins/jaws/jdbc JDBCCommand.java
>
>
> > we are discussing exactly the opposite, I am deeply convinced that this
> > belongs in jaws
> >
> > marcf
>
> Sorry, I rolled back the code before you responded. If you want me to put
> it back in, I will it takes about 10 minutes. I think I made a
> mistake and
> made the first change to quick (it was easy) , and I think we
> need to figure
> out what we are doing (design before code).
>
Again, I'll reiterate, I strongly suggest NOT defining transaction isolation
levels in JAWS nor at at any other level other than in the definition of a
connection pool or other data resource. You'd really have to redesign and
rewrite how JAWS interacts with data resources and frankly, I think the
abstraction that is already there provides the most flexibility(it uses
javax.sql.DataSource) in plugging in DataSources other than the stuff in
jbosspool. In fact, the EJB 2.0 spec supports some of the things I'm trying
to say here. "Isolation Levels 17.3.2"
"The following are guidelines for managing isolation levels in enterprise
beans.
- The API for managing an isolation level is resource-manager specific.
(Therefore, the EJB architecture does not define an API for managing
isolation level.)
- If an enterprise bean uses multiple resource managers, the Bean Provider
may specify the same or different isolation level for each resource manager.
This means, for example, that if an enterprise bean accesses multiple
resource managers in a transaction, access to each resource manager may be
associated with a different isolation level.
- The Bean Provider must take care when setting an isolation level. Most
resource managers require that all accesses to the resource manager within a
transaction are done with the same isolation level. An attempt to change
the isolation level in the middle of a transaction may cause undesirable
behaviour, such as an implicit sync point."
Theres more interesting stuff, but I don't feel like typing it in.
Bill
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
