Ok thanks Niclas. More queries: What are we doing here Artifact artifact = getDefaultImplementation( dir, line )
What is an artifact in Avalon/Merlin terms and what is an implementation. -----Original Message----- From: Niclas Hedhman [mailto:[EMAIL PROTECTED] Sent: Friday, January 23, 2004 10:20 AM To: Avalon framework users Subject: Re: merlin container code The Subject is "Bootstrapping of Merlin", but the thread contains this as the only post, and the post is complete in this mail. What happens was, that I queried roughly the same thing to Stephen privately, and he gave this explaination, so I forwarded to the dev@ as I thought it to be of general interest. Please note that these APIs are not 100% solidified, and may change in the near- or mid-term future, as we will investigate what IS the public API of Merlin. Cheers Niclas On Friday 23 January 2004 10:03, Vikas Phonsa wrote: > Yeah I don't subscribe to the dev list. But I did a rough search in the dev > archive after reading ur email yesterday but couldn't find it. but I didn't > search hard.. Do you have the subject of that post handy. I would like to > read that. > > Thanks > > Vikas > > -----Original Message----- > From: Niclas Hedhman [mailto:[EMAIL PROTECTED] > Sent: Friday, January 23, 2004 10:02 AM > To: Avalon framework users > Subject: Re: merlin container code > > On Friday 23 January 2004 09:48, Vikas Phonsa wrote: > > So all the steps that are taken in CLI and AbstratMerlinTestCase are the > > ones that we need to start up Merlin and have it load our components, > > right. > > I get the feeling that you don't subscribe to [EMAIL PROTECTED] and haven't found > the > answer there, so I am reposting the Merlin bootstrap sequence. > > > > 1. user creates a new DefaultInitialContext > - this provides the micro-bootstrapping facility > 2. user creates an Artifact reference > 3. user creates a new DefaultBuilder that uses the > initial context and artifact > 4. user request the Builder to build a factory > - builder looks at the artifact and tries to locate > meta data about the classloader hierachy that it > needs > - builder pulls in all of the dependent jars and > creates the classloader hierachy > - builder instantiates a factory using the new > classloader and returns this to the user > 5. user gets the factory > 6. user requests from the factory the default criteria > (a map of default values) > 7. user parameterizes criteria (setting this and that) > 8. user requests the factory to create a new instance using > the criteria > 9. done - merlin is running (or whatever the artifact is > referring to) > > > Hope this helps in creating your own bootstrapper. > > Cheers Niclas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
