avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Hammant <Paul_Hamm...@yahoo.com>
Subject Re: ComponentManager interface
Date Mon, 11 Feb 2002 08:14:17 GMT

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
>I realize that JNDI seems a bit heavy for the immediate use but the
>advantages of using the standard registry interface outweigh the negatives
>I'm sure this has probably been hashed over previously - so sorry.
>>-----Original Message-----
>>From: Berin Loritsch [mailto:bloritsch@apache.org]
>>Sent: Sunday, February 10, 2002 5:07 PM
>>To: Avalon Developers List
>>Subject: Re: ComponentManager interface
>>Stephen McConnell wrote:
>>>Pete suggested:
>>>This is perfect!
>>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!
>>To unsubscribe, e-mail:   
>>For additional commands, e-mail: 
>To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
>For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>

To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>

View raw message