Leo Simons wrote:
Hi gang,
Hi Leo!
[EMAIL PROTECTED] wrote:
Steve,
Really quick I wanted to say the Map idea may be better I just did not know if it was definitively. Might be the better route to go.
disagree :D
1. I think KernelParameters should go into a seperate package that other packages (such as kernel) depend on. This will make it easier when creating the bootstrap process.
disagree! Recognize the tight coupling between config and component and reflect it :D
Yes - I agree when looking at the biog picture - however - break this down into operational stages. The very first stage is to build the classloader so that you have access to classes like Configuration, Kernel, etc. For that primitive step - we need to aggregate the parameters then enable location of the jar files needed to do this. This means loading the repository api and impl, kick-starting the repository, then using repository, build the classloader that will contain the kernel classses.
I.e. seperate stages are:
(a) establish parameters for repository bootstrap (b) build repository classloader (c) boostrap repository (d) load and bootstrap the kernel loader
Steps (a) and (b) use classes in the system classpath - hense the seperation.
Cheers, Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
