I have not looked in depth, this is just my first step towards understanding the Merlin project.
Ok, in Merlin's CVS there are several "sub-sub" projects:
assembly assembly-spi merlin-cli merlin-core merlin-extensions merlin-plugin merlin-smp merlin-spi meta meta-spi meta-tools
That's alot of things to try to figure out what they mean. I assume all the "-spi" directories refer to "Service Provider Interface", and the "-cli" directory refers to "Command Line Interface". That seems self explanatory.
So we have Assembly, Merlin, and Meta as the main categories of "Merlin" projects. When I see these categories this is what I think:
Assembly: matching service implementations with the lookup names for
client services.Merlin: The "Merlin brand" container.
Meta: The information about services.
Please stop me if I'm wrong.
Assembly has the basic package and the SPI package. I assume this means the SPI only has interfaces and the basic package has the implementations.
Meta has the basic package, the SPI package, and the tools package. I assume this follows the same pattern for Assembly, with the tools package being used for ANT tasks and Maven integration.
Merlin has CLI, Core, Extensions, Plugin, SMP, and SPI. I can assume that SPI is like assembly's and that Core is where the kernel live. CLI is for the command line invokation of Merlin--not necessary for servlet based systems. The difference between extensions and plugins is a bit fuzzy for me. The names suggest synonyms. Are extensions referring to Lifecycle Extensions and plugin referring to kernel plugins? The only thing in this list that is a complete mystery to me is the SMP directory. To me SMP means Symmetric Multi-Processing, which is something that Merlin should be designed to work within from the ground up. I believe it is referring to something else, so I have to ask what.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
