setHarURL was needed simply to allow the deployer to inject this value into the mbean. Use of this at runtime or through the console is highly discouraged ;)
Another thought is that in the scheme y'all are proposing (provided multiple interceptors can process the deployer init stuff) we could simply have an additional Hibernate-specific interceptor which checks the deployment's mbeans for the Hibernate mbean and injects the url. Then you would not need ServiceMBeanSupport exposing the URL attribute at all and could still get away with no specific HARDeployer. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3874112#3874112 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3874112 ------------------------------------------------------- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
