Hi,
I'm confused. Are you saying that the behavior mandated by the JCA spec is
not sufficient to guarantee that every connection handle will used in the
correct transaction? If so, is this not a deficiency in the spec? If not,
what is the JBossConnectionListener for more specifically?
thanks
David Jencks
On 2001.05.05 23:51:29 -0400 Toby Allsopp wrote:
danch wrote:
Does anyone have opinions on whether this would be a good feature or
not? The 1.1 spec does not specify how isolation levels should be
handled, except for BMT session beans, and by saying/implying that
beans
can call resource manager specific APIs to set it themselves
(carefully).
If this seems like a good idea, should this setting be in jboss.xml
(and
cover BMP and CMP entities as well as sessions), or in jaws.xml
(covering _only_ CMP entities, since others are free to call the
resource manager's APIs)?
What do mean by cover BMP and CMP entities as well as sessions? This
can only apply to JDBC connections, right? Do you propose to set the
isolation level when a connection handle is obtained by the bean? If
so, this should probably be implemented using the same mechanism I have
in mind to implement beans hanging onto connection handles across
transactions.
JBossCX defines the JBossConnectionListener interface for this purpose,
although it is not currently used. The idea is that when a resource
adapter gives out a connection handle, the app server is notified so
that it can make sure it is participating in the correct transaction.
It would be easy to extend that to any transaction-specific setup we
wanted to do.
Toby.
___
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
