Larry, JNDI as a choice of access mechanism to Phoenix services, but not the default IMHO. I plan do deliver a JNDI access point for AltRMI services (thou I am lacking a good example of a provider), which would allow any transported service to be JNDI looked up.
Framework lookup (the IoC way) is soooo elegant. JNDI is very heavy and it feels "thunky" for a default resource lookup. - Paul >Perhaps now is a good time to reintroduce the idea of actually using JNDI? > >I think that it would be an acceptable alternative to introducing a new >package. > >I realize that JNDI seems a bit heavy for the immediate use but the >advantages of using the standard registry interface outweigh the negatives >IMHO. > >I'm sure this has probably been hashed over previously - so sorry. > >>-----Original Message----- >>From: Berin Loritsch [mailto:[EMAIL PROTECTED]] >>Sent: Sunday, February 10, 2002 5:07 PM >>To: Avalon Developers List >>Subject: Re: ComponentManager interface >> >> >>Stephen McConnell wrote: >> >>>Pete suggested: >>> >>> >>>>framework.service.ServiceManager >>>>framework.service.Servicable >>>> >>>This is perfect! >>>Steve. >>> >>> >>Not for what has been discussed. I.e. a lightweight form of JNDI. >>Service is even more narrow than Component, as Service is a specific >>type of Component. >> >> >>---------------------------------------------------- >>Sign Up for NetZero Platinum Today >>Only $9.95 per month! >>http://my.netzero.net/s/signup?r=platinum&refcd=PT97 >> >>-- >>To unsubscribe, e-mail: >><mailto:[EMAIL PROTECTED]> >>For additional commands, e-mail: >><mailto:[EMAIL PROTECTED]> >> > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
