That's ok with me for now, but its yet another expansion of the xml parser usage into
a context it does not belong. We should not be doing this in 4.0.
 
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx

________________________________

From: [EMAIL PROTECTED] on behalf of Bill Burke
Sent: Wed 1/7/2004 2:52 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] pluggable tx retry handlers





Scott M Stark wrote:

> This is really not a container level configuration, rather its
> configuration info for
> the tx interceptor, but we don't support that capability well.

I just added support to allow you to define an interceptor as
XmlLoadable (haven't committed) this is how I did the tx retry stuff.

  The mbean
> approach
> with an attribute on the tx interceptor that references the mbean
> approximates
> this. There has to be some pluggibility as I doubt every deployed
> application
> wants the same retry logic.
> 

Ok, then I can keep it as I've implemented it though.

You would do
<interceptor>org.jboss.ejb.plugins.TxInterceptorCMT
   <retry-handlers>
     <handler>com.stuff.myhandler</handler>
   </retry-handlers>
</interceptor>

Bill
--
================
Bill Burke
Chief Architect
JBoss Group LLC.
================

 

<<winmail.dat>>

Reply via email to