On Tuesday 23 December 2003 04:22, Marco Tedone wrote: > 3) Set up the HelloWorld example > 4) Create an HelloWorld client that uses the HelloWorld service
Perhaps you have not noticed that there are a set of tutorial samples as well. Not sure where they go distribution-wise, but I know you work with the CVS, so look in; avalon/merlin/platform/tutorials I think this will also give some "tidbits". :o) > 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. This is a "controversial issue". Inversion of Control means that we intend to remove the ability for components to "go out and find" on their own. However, no container prevent stuff like this from happening (yet), but I doubt you will see something that generic. > 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? Not sure what you mean. merlinx.sh -execute someComp.jar will pick up the /BLOCK-INF/block.xml and create a deployment scenario from that file. merlinx.sh someBlock.xml where the block XML file given will describe the deployment scenario. In which case you can have loads of "assembled" applications with the blocks you have at your disposal. > 3) If so, how much would it cost in term of time > and resources to make the Merlin kernel a RMI application? More than we want to believe. To make it RMI only is no big deal, and I think there are some work already done in that area (pre-my time). But _I_ want to see Merlin be capable of being a Jini containment platform, so that services that are deployed in Merlin would join the federation of Jini services. This is a lot trickier to use, as we must first make the "static binding" of Merlin today into a "dynamic binding", and allow services to "come and go", i.e. other services should not only have "lookup" but also be registered as some form of "availability listeners" to the services they require. Once this contract is worked out in detail, we will be able to handle both Jini and "reloading" of services/components on the fly, not currently possible. > 4) In few words it would be nice to have some hot > deployment services This is currently not supported. This is Phoenix feature, that we would like to port into Merlin at some point. Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
