On Friday, January 24, 2003, at 11:53 AM, Sacha Labourey wrote:
oh yes! This problem really involves all management parts i.e. how we wantI'd like to see more advantages before undertaking such an enormous project.
to be able to store the config, modify the config, have config repositories,
etc. Furthermore, we need to take in account in this new design the
really-missing-"restart"-feature which is not equivalent to the stop-start
semantic.
Why not?
I was planning to move the dependency logic from ServiceController to ServiceContext and make ServiceContext an mbean interceptor. It would also block calls when state was not started. If you change a set of attributes, it would consult the metadata to see what lifecycle state it must downgrade to, go to it, and go back to "started". Do you see something wrong with this plan?
We must really implement the restart trick for 4.0 as it is one of the only
way to cleanly implement the "valve" trick (block the valve for new
invocations as we cycle the app/service).
david
Cheers,sacha ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
