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.
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. The reason I'm wanting to do this is b/c I'd like to begin porting a legacy application to merlin, but not all of it can go right away. I was thinking that maybe I could migrate some services to an embedded merlin container, provide an API wrapper so the stuff that can't be migrated right away can still have access to the migrated services, and over a period of time enrich the API with more migration. One day, everything would be migrated, and I throw away the API wrapper/embedded container, and just deploy my migrated components in a standalone merlin server. Does this sound like a reasonable roadmap? Timothy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
