Dear Nicolai, few things about my involvment: 1) I usually develop after work using my spare time (i.e. I am a novice programmer)
2) I don't know anything about SOAP (the only thing I know is that is involved with Web Services, thus I don't know anything about web services :) 3) The time I can dedicate to this and other projects is limited, as I should share my spare time between my studies, open-source projects, the gym and my girlfriend (the order is not meaningful! :) 4) I just obtained the Java Programmer Certification and now I'm studying for the Developer's one. This means that I'm new (or I am studying) concepts like RMI, GUI interfaces, Logging, Threads, IO and open-source projects give to me the possibility to program professionally without being employed (and, SIGH!, paid:) 5) I'm just getting started with Avalon and Merlin following a loooong path (you won't believe this, but everything started from a portal!) and therefore I am not very familiar with the general architecture although I'm reading the documentation and I believe soon I'll be able at least to understand what's going on... That said.... It seems to me that it's already possible for Merlin services to use other Merlin services. What my RMI solution would like to realize, is to make the Merlin services available for any client inside/outside Merlin. At the end Avalon is a great framework for business logic, and it would be a shame to limit its services locally to Merlin, wouldn't it? I am also new to security but I would like to learn, therefore I would be interested in contributing in a security solution for Merlin (which is among the requirements, if I am not wrong). Marco ----- Original Message ----- From: "Nicolai Wadstr�m" <[EMAIL PROTECTED]> To: "'Avalon framework users'" <[EMAIL PROTECTED]>; "'Marco Tedone'" <[EMAIL PROTECTED]> Sent: Monday, December 15, 2003 9:32 PM Subject: RE: A standard for the organization/naming convention of Merlin Repositories > > -----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]
