Schaible, J�rg wrote:
The purpose of the bootstrap package is to isolate classes that are loaded by the JVM into the classloader so that the bootstrap classes can setup the internal and public classloaders based on a kernel defintion. This means that the bootstrap loader has to be completely independent of the Merlin and related classes (i.e. any bootstrap will be using well documented keys as distinct from key by reference).Hello Steve, I looked at the Merlin class in bootstrap to get an idea about the initialization for my webapp and I recognized, that I cannot access at least these system constants like Merlin.MERLIN_KERNEL_LOADER_CLASSNAME or such simple things like Merlin.getVersionString(), since the class is in the default package and the members private anyway. Is this so intented?
In your case (embedding a kernel in a web-app) you would be creating and configuring an instance of DefaultKernel - and in effect - comming up with something equivalent to the DefaultKernelLoader but focussed on establishing the kernel relative to servlet supplied information.
Short term priorities (for me) are to:
a) improve the CLI bootstrap process (more consitent and
easier to use)
b) some refactoring over on the Assembly project (make some
things cleaner and easier to work with)
c) put in place some meta generagion tools
After that I'll be able to spend some time on the web-app side.
Cheers, Steve.
--
Stephen J. McConnell
mailto:[EMAIL PROTECTED]
http://www.osm.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
