> > Based on posts over the last week or so, combined with what is in > > place on the subject of kernel embedded, I'm trying to figure out a > > good direction. > > > > Context - current embedding approaches: > > > > 1. the kernel/bootstrap package (a CLI based loader) > > 2. the maven merlin plugin (maven project context) > > 3. abstract unit test in kernel/unit (maven project context) > > 4. Alexis Agahi' work on re. Avalon in JBoss and OpenIM > > 5. Timmothy Bennets work on Jetty > > 6. Peter Courcoux work in embedding inside a web-app for Turbine > > > And am I plain stupid or what?
You're too hard on your self. I would not be using Merlin if I thought that. I didn't include the ldapd effort linked > to Alex Karasulu (incubator project). That's a project that is > fundimentally interested in embedding Avalon. Think contaner embedded > inside a JNI context - lots of really cool local and remote stuff. If Thanks for pointing us out. Basically a server side JNDI LDAP provider on the first attempt to create a JNDI context initializes the kernel. This will happen (hopefully by this week) within the provider's InitialContextFactory implementation. If the required modules are not up then they are started and processing continues. If they are already up then np. I'm glad btw to see a generalized approach to handling embedding. Also perhaps we can get a list of the parameters required and optional of the kernel to bring it up. This would help understand what's going on. Also I think I'm a good candidate as a guinne pig to see how the embedding process goes. I'll try to post about my experiences and keep a journal or something of them. That way we can make sure the process is easier for those that come later to embed Merlin's kernel. > I've missed any other embedded scenarios - let us know! > > Cheers, Steve. > Thanks, Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
