Well, this make me think to the idea of having Avalon components natively relised as RMI servers. Today I was thinking in building a Naming Service that follows the Context approach. The Naming Service could then store components by Context/subContext allowing for quite advanced query features.
Marco ----- Original Message ----- From: "Nicolai Wadstr�m" <[EMAIL PROTECTED]> To: "'Avalon framework users'" <[EMAIL PROTECTED]> Sent: Monday, December 15, 2003 12:35 PM Subject: A standard for the organization/naming convention of Merlin Repositories Hi, I am new to the list (but not to Avalon and Merlin), I couldn't help noticing that different projects use different structure for the component repository (Merlin itself and for example Phoenix JMS). As far as I have seen in the docs or otherwise, I could not find anything about a standard for naming the components in the repository (except for version number of the .jar files), and this creates a problem when putting together components from different sources, so it would make a lot of sense to create a standard of how components should be named in the repository because these names are used in references in each block.xml component, one examples of how this could be done: All components (and any library jars) from apache go under a directory called apache (e.g. system/repository/apache/jars/projname-componentname-0.0.0.jar), right now the Avalon core components are named in a mix from different projects. My own components would go under my company just below the repository directory? If an naming convention like this were imposed in the documentation, in would insure that plugging together components from different vendors as intended with COP model would be more easily obtainable. Right now I need to duplicate the .jar files for some core components or I need to repackage a number of third party components that I use. Another approach might be to add support for aliases in the Merlin repository (such as an XML file where I would declare alias definitions for components), but I would rather see a standardized naming convention in the repository. Any thoughts or comments? Best regards, nicolai wadstr�m ---------------------------------- mailto: <BLOCKED::mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] website: <BLOCKED::http://www.wadstrom.net/> http:// <BLOCKED::http://www.wadstrom.net/> www.wadstrom.net/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
