I'm not seeing how IOC is sufficient to bring up a web container for example. There still needs to be a start notion that allows the service to configure all of its internals it seems. How would start on the service interceptor be able to do this?
anonymous wrote : | I actually feel lifecycle is unnecessary if read-ahead and IOC was implemented. It would be replaced by ordered configuration and valves. The user would have two options start/stop the valve or deploy/undeploy the service. | | One solution would be to run core services/deployers in "ring zero" | a sort of controlling sub-machine/extensible kernel. This would make other services slightly second class citizens. | This still does not solve the problem generally, e.g. | 1) how to allow pluggable logging (currently implemented with a boot.log and server.log) | 2) how to run the boot under a security context and still have pluggable security | 3) what if you want your mbean persistence from the db for your core services when the db connection isn't deployed until later | | It's almost like you a need a separate bootstrap "process" | that boots enough to configure the main machine before being discarded in favour of it? A bit like the bios/boot block in the pc. | | Regards, | Adrian | <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3824596#3824596";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3824596>Reply to the post</a> ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
