Thanks for your reply -danch.
> Isolation level can't be set declaritively in the > descriptors. You can set it
>programatically on connections > you retrieve from the pool.
This is dangerous. You have to make sure that you restore the connection existing
isolation level before it is put back to the pool.
Otherwise you will create potentially serious problems.
I believe the right way to do it is to actually ask for a datasource connection that
would be of a particular isolation level.
The isolation level should be set to a newly created connection and that should be
done by the container.
Therefore, as far as the programmer is concerned, they should ask for a particular
datasource that they know would be of a particular isolation level. One could set
multiple datasources in the jboss.jcml file and setting their isolation level.
Something like:
<attribute name="IsolationLevel">repeatableRead</attribute>
Or alternatively, one could declaratively set the isolation level on a per-method base
for a session bean in the ejb-jar.xml file (JRun does it as an env-entry).
> It will be possible to set this in the future, although the > current thinking is
>that this will be a JAWS (CMP) only feature.
If you do BMP you should still be able to declaratively set the isolation level. I see
no reason why it should be a CMP only feature.
I didn't see a lot of discussion on the jboss-user mailing list about it. May be the
jboss-dev one is a more appropriate place?
Cheers,
Yann.
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
