Help me out on my thinking about composition within merlin. Make sure I'm understanding at least one of the purposes of composition...
Here's an example of a server application I'm looking to build with merlin. It will need: (1) an embedded web server (2) an embedded database (3) an embedded FTP server (4) an embedded mail server (5) plus my "application" stuff that I've either already built for phoenix, or stuff I still need to build James already works with merlin, and I've recent gotten the Jetty-Phoenix, HSQL, and FTP server phoenix blocks migrated to run under merlin. Each of these "servers" have their own block.xml files (which I refer to as a container descriptor -- don't know if that is correct nomenclature). Separately, they are certainly their own application. But if I combine all the block.xml files together into a single block.xml to make the beginnings of the application I'm really interested in, then: (1) the block.xml is already getting very complicated and large with all the configuration stuff, and (2) the original "standalone-ness" of the individual server blocks begins to get lost. Is this what composition is for? Each of these "servers" have their own block.xml, but when I want to make the "uber-server", I construct a new block.xml that "imports" these individual block.xml files? Is that the idea? Timothy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
