> > Basically what makes sense is one set of docs the describe the usage of > the template. This should be seperate from the template itself. The > usage docs would then go through the steps - download, customize, > populate, build, etc. >
If you don't mind I would write a documentation for the following: 1) Download and install the template 2) Create a copy of the template (The HelloWorld example) 3) Set up the HelloWorld example 4) Create an HelloWorld client that uses the HelloWorld service I succesfully created a component which uses the HelloWorld Service now. However, I've got some questions: 1) Would it be possible to using a naming service to register services/components? If so, it would be nice to have a feature like the following: when registering a service, all the components would be registered automatically. 2) I executed maven merlin:simulate under /impl and all the components have been executed. I'm sure this is not the only way components can be ran in Merlin, otherwise it would be too limitative. Users may want just to run a component rather that all of them (sequencially?). How could this feature be enabled? 3) I can guess that when executed, Merlin registers services somewhere and make them available to other components. Doesn't this seem very similar to a distributed application? If so, how much would it cost in term of time and resources to make the Merlin kernel a RMI application? 4) It would be nice to have Merlin running (even if without services) and listening for deployments. In few words it would be nice to have some hot deployment services (like JBoss and Tomcat) and having Merlin as a container. I'm sure there is a way to run Merlin without services, just for the pleasure to see the container running, but I don't know how. What I would avoid, is to be constrained to run several instances of Merlin for different applications. It would be nice to have one instance that deploys all the services. Marco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
