> 1. Related to these problems is the question of how we should store > "persistent" mbean attributes and the desired relationship between these > persistent attributes from storage and those from a possibly modified > config file. Remember the bad old days of jboss-auto.jcml? That is gone > but no replacement has arrived....
I would like to hear what the JMX experts have to say about this one... > 2. You should be able to deploy jetty stuff as a (bunch of) jars + > jetty-service.xml all in deploy. The mbean config should wait for its > classes, if it happens to get deployed first. Is this not working > properly? Have you tried it? No did not try... > 3. IMO there is no reason not to have everything (not explicitly on the > boot classpath (?)) in lib redeployable. I'm not sure exactly what is > needed, but I doubt it is a large change. Yes, with the exception of the boot archives we should be able to redeploy any part of the system. > If you are seeing specific mbean dependency problems, please let me know > what they are. I just needed to setup a static webapp. I turned jetty-plugin.sar into jetty- plugin.jar (in lib/) and jetty-service.xml, which is working fine. --jason ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
