From: <ste...@jb...> - 2005-07-29 14:34:40
|
So to be completely clear... I totally agree with you that it is completely silly having a ~400 line class (HARDeployer) whose sole resposibility is to set a single MBean attribute (just look at my comments in HARDeployer ;). If there were some other simple way for an MBean to know about the DeploymentInfo (or even just the DeploymentInfo.url) from whence it came, I'd be all for using that instead of a full deplyer. But in my limited knowledge of the AS internals, there does not seem to be such a simple alternate approach. Please, if I am wrong, correct me. In the end, I think the "aggresive scanning" of the deployment classpath entries is very, very good idea. But based on the previous discussion regarding multiple SessionFactoys, I think it makes sense as an option on the MBean rather than as the defacto way in which mappings are discovered. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3887304#3887304 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3887304 |