Hi Jim / Jeremy, I have been able to go forward quite a bit.
- Which is the scdl into which I must add the RMIHost component. I added it first to the system.scdl in SCA-API project. But that did not get picked up by the loader. When I debugged I figured out that it was the system.scdl in the SCA-Test project that was being loaded for system components. So added it there and it did get picked up. Is this right? There is something that I am missing here.. where should I be adding this component actually. - I have added 'Module' scope for the RMIHostImpl and have the eager init decoration as well. - I have added the autowire annotations to the constructor of the RMIBindingBuilder. When I run, the RMIHostImpl is picked up and injected into the builder. But then I have having some strange exceptions in the DirectoryScanner and in the creation of the target invoker. I shall work to get over this and see if I can post a patch tonight. Thanks - Venkat On 8/14/06, Jim Marino <[EMAIL PROTECTED]> wrote:
On Aug 13, 2006, at 11:00 PM, Jeremy Boynes wrote: > On Aug 13, 2006, at 10:42 PM, Venkata Krishnan wrote: >> - each registry is identified by a port on which it runs. I am >> not sure >> how hostname can be used for services. However, for references >> host names >> has a role to play. Right? > > For services it would determine the address that the port would > apply to. The default (0.0.0.0) would be all addresses on the > machine but for multi-homed machines it is quite often useful to be > able to specify a particular interface. > >> - RMI Host will be the interface thro which RMIBinding will register >> services into one of the registries (based on the port number >> specified) >> >> Can you please point me to some code that I can emulate to >> implement RMI >> Host in terms of how it should be implemented as a system >> component that can >> be autowired into the builder. Right now I am looking at >> LoaderRegistry to >> understand the programming model for this. Am I on track? > > That's as good as any. If you start with a POJO and just decorate it according its methods with @Init and/or @Destroy as needed you should have most of it. I'll keep an eye out and help when needed. Jim > -- > Jeremy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]