So is the capability of remotely starting/stoping a jboss instance implemented or investigated?
How it will be done? Replying to Chris' post, we would persist the properties of any module we create (and overwrite them every time we edit/regenerate that module). So we will always have the last good property image, as long nobody screws up with the console-generated modules. The delayed deployment is also an option. We can store delayed deployments in a different location and upon startup, as long as the deployment service is started from ./conf/jboss-service.xml, it could overwrite those delayed deployments *before* the DeploymentScanner starts... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862606#3862606 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862606 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
