> -----Original Message----- > From: Marco Tedone [mailto:[EMAIL PROTECTED] > Sent: den 15 december 2003 16:19 > To: Avalon framework users > Subject: Re: A standard for the organization/naming > convention of Merlin Repositories > > 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.
RMI exposure sounds interesting and if built the right way could transparently allow components to be used by other components with-out needing to know where they are being executed. Where they are executed would be determined by configuration instead. A great idea indeed! If a naming convention/repository organization spec would state that a component should package it's public interface and the implementation separate (as the avalon components themselves are packaged today), Merlin could automatically download the Interface part during the assembly phase, and connect to the remote server executing the code. This solves a number of issues that are always common when using EJB's and RMI. What are your thoughts on supporting SOAP as well? Although RMI and/or SOAP exposure of the components would require a bit more sophisticated security features than currently available in Merlin I would think. Also some verification to code-signing signatures in the .JAR's seems like a good idea (even without RMI and SOAP exposure), when doing automatic download of code as Merlin does through remote repositories. / Nicolai --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
