> Using the AbstractMerlinTestCase as an example, I was thinking of embedding > a merlin container as part of the implementation of a Java API. The API > could be called by any piece of Java code and the fact that the > implementation of the API is actually being executed/managed with a merlin > container would be hidden from the client of the API.
This is entirely the goal of the server-side JNDI LDAP provider for ldapd you basically use the JNDI API and under the hood the implementation fires up an LDAP server. Steve and I have been working towards this but to get there the right ClassLoader structure needs to be assembled for the container. The Repository API not only downloads jars to allow for a small embedded jar footprint but it builds the ClassLoader using dependency information associated with Merlin kernel implementation version used. We are trying to finish off the repo stuff to be able to build a simple kernel loader that loads and runs the kernel with your application. > The services of one (or more) of the components living in the embedded > container is something that I wish to provide access to the API client via > methods in the API. It's not clear to me how to *export* services out of > container. You'll need to do reflection unfortunately because of the ClassLoaders. > Does this sound like a reasonable roadmap? Yes very straight foreward. Alex
reply
Description: null
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
