This is really not a container level configuration, rather its configuration info for the tx interceptor, but we don't support that capability well. 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. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx
________________________________ From: [EMAIL PROTECTED] on behalf of Bill Burke Sent: Wed 1/7/2004 1:58 PM To: Jboss-Dev Subject: [JBoss-dev] pluggable tx retry handlers I'm currently writing pluggable TX retry handlers so that you can configure JBoss to automatically retry transactions for other exceptions other than ApplicationDeadlockException i.e. Oracle deadlock, MySQL cluster failure, etc. The question is, should this be pluggable per entity container and thus have to define the handlers per container? This is what I have implemented currently and thought that it might be overally complicated as you would have to define it for every container. The other approach would be to just define this thing for the entire app server in an MBean. Thoughts? Thanks Bill -- ================ Bill Burke Chief Architect JBoss Group LLC. ================ ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
<<winmail.dat>>
