There is a bug in the javax.management.monitor.Monitor class that prevents me from using StringMonitors. I know how to fix the code, but I'm looking at a production environment where I want to deploy the change with a minimum of effort. In particular, I don't want to get into building and maintaining my own version of Jboss 3.2.5. Is there any way through configuration - properties files, environment variables, etc. - to direct a booting Jboss to pick up my fixed version of Monitor before it loads jboss-jmx.jar? jboss.patch.dir sounds promising, but I don't know how to get it to function. Thanks.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859585#3859585 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859585 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
