Are you saying, a specialized class loader that links loading of certain classes to activation of related services?
Or the simpler proposition, that services be lazily created as needed. -- Howard M. Lewis Ship Creator, Tapestry: Java Web Components http://jakarta.apache.org/tapestry > -----Original Message----- > From: Jules Gosnell [mailto:[EMAIL PROTECTED] > Sent: Friday, August 08, 2003 5:03 PM > To: Geronimo Developers List > Subject: [components] - lazy loading... > > > a chat with a friend, Shane, at work today produced these thoughts.... > > Imagine that rather than having a set number of > configurations which all > load every service at startup, Geronimo could load just the > components > needed to provide the services required by your deployables... > > e.g. you are doing web development, so when you start > Geronimo it just > loads the webcontainer component and deploys your webapp. You webapp > decides to load a javax.naming class so the JNDI service is > brought on > line, it loads a javax.mail class and looks up a mail service > in JNDI - > the mail service is brought up... etc > > If we could lazily load services as required, startup time would be > greatly reduced, footprint as well, and the distributions > complexity too > - since we could just ship everything and only what was > needed would be > used. > > just a thought to file away for a rainy day :-) > > > Jules > > -- > /************************************* > * Jules Gosnell > * Partner > * Core Developers Network (Europe) > * http://www.coredevelopers.net > *************************************/ > >
