this is a feature we definitely want. this involve refactoring of the code base, to pull out generic deployment service in order to handle multiple subservers.
your point are valids and the scenario would be like : - have a super .sar that would contain the web app intercepter - each portal server would be a .sar with the .war embedded 1. I did it with a codebase some month ago and I had it working but I lost it in HD crash :-( 2. it is necessary in order to setup the BootStrapContext that contains the server ServletContext and ClassLoader. It could be sort of avoided by using a registry when the listener would put the BootStrapContext under a key and then the traditional .sar service would pick it up. Mainly the ServerManager needs it in order to load its configuration. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872100#3872100 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872100 ------------------------------------------------------- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
