> |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...
>
> ok but these will be leveraged by new caches in JBoss 3.0
>
>
>
> so I would imagine that each application can set its own datasource
> isolation level, (different kinds of bean). So it IS user configurable
> right???
>
> Also how does it play with the datasources, if the datasource is shared
> across applications and different tables support different locking
policies
> (say one table is RO the other RW) can the driver support sequential
> "setIsolationLevel" that only applies to the record and or table touched?
> marcf
>
Right now this the jaws and jbosscmp code only support datasource per
application. When we implement datasource per bean, we can have isolation
level per bean. This leads to the intresting situation with EJB-QL queries
that thouch multiput beans. May be we need to specify an isolation lever for
each query. Havn't thought about it much. Right now you can only set it
for the entire ejb-jar.
Just tell me when you get the cache stuff figgured out and I can update jaws
and jbosscmp to support what ever you want.
-dain
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
