Right, I agree, start is not a configuration issue, and we don't use it as such now. It is a lifecycle op to notify the component to use the current configuration to bring the component into the start state. In a pojo framework with only aspects/interceptors introducing the service level functionality start can be handled outside of the component.
For integrating containers like the web container which already have a lifecycle notion its easier to simply delegate the start op to the component to bring up its connectors, etc. Its not that the web container does not support IOC, its already does by virtue of the mbean attributes. Taking all of the configuration info to a running web container is no something I can see being done by an IOC framework though. <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3824609#3824609";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3824609>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
