Return-Path: 
 <dev-return-25538-apmail-avalon-dev-archive=avalon.apache.org@avalon.apache.org>
Delivered-To: apmail-avalon-dev-archive@avalon.apache.org
Received: (qmail 82597 invoked by uid 500); 7 Aug 2003 03:48:15 -0000
Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@avalon.apache.org>
List-Subscribe: <mailto:dev-subscribe@avalon.apache.org>
List-Help: <mailto:dev-help@avalon.apache.org>
List-Post: <mailto:dev@avalon.apache.org>
List-Id: "Avalon Developers List" <dev.avalon.apache.org>
Reply-To: "Avalon Developers List" <dev@avalon.apache.org>
Delivered-To: mailing list dev@avalon.apache.org
Received: (qmail 82564 invoked from network); 7 Aug 2003 03:48:15 -0000
Received: from web20914.mail.yahoo.com (216.136.226.215)
  by daedalus.apache.org with SMTP; 7 Aug 2003 03:48:15 -0000
Message-ID: <20030807034825.19890.qmail@web20914.mail.yahoo.com>
Received: from [203.197.16.233] by web20914.mail.yahoo.com via HTTP;
 Wed, 06 Aug 2003 20:48:25 PDT
Date: Wed, 6 Aug 2003 20:48:25 -0700 (PDT)
From: Vinay Chandran <vinayc77@yahoo.com>
Reply-To: vinayc77@yahoo.com
Subject: Re: Containment model @ java.beans.
To: Avalon Developers List <dev@avalon.apache.org>
In-Reply-To: <3F310A99.6080208@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

After a quick dirty look , java.beans's BeanContext
has a service provider+service registration+ service
revocation features.It also have events associated
with these too.
Thus it could actually serve as a mini-
container resolving intefaces to concrete
implementations.

Interesting aspect out there was getService() call 
had the requestor object as an argument for some
reason along with the interface or class your are 
requesting & selector that might be applied.

Regards,
Vinay


--- Berin Loritsch <bloritsch@apache.org> wrote:
> Niclas Hedhman wrote:
> 
> > Niclas wrote;
> > 
> >>Berin wrote;
> >>
> >>>Vinay Chandran wrote:
> >>>
> >>>
>
>>>>http://java.sun.com/j2se/1.4.1/docs/guide/beans/spec/beancontextTOC.fm.html
> >>>>
> >>>
> >>>I took a quick look.  I noticed with the
> BeanContext and the
> >>>associated interfaces, that all child components
> were expected to
> >>>extend
> >>>java.awt.Component and all child containers were
> expected to extend
> >>>java.awt.Container.
> >>
> >>I also took a quick look, but can't find this
> limitation.
> > 
> > 
> > I found this on page 15 in the PDF document;
> >
>
http://java.sun.com/products/javabeans/glasgow/beancontext.pdf
> > 
> > <quote>
> > Although not required, many BeanContexts may be
> associated within a
> > presentation hierarchy
> > of java.awt.Containers and java.awt.Components. A
> Container cannot implement
> > BeanContext directly1 but may be associated with
> one by implementing the
> > BeanContext-
> > Proxy interface described herein.
> > </quote>
> > 
> > So I think you misunderstood, Berin.
> 
> Very possible.  As I said it was a quick look.
> 
> 
> -- 
> 
> "They that give up essential liberty to obtain a
> little temporary safety
>   deserve neither liberty nor safety."
>                  - Benjamin Franklin
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail:
> dev-help@avalon.apache.org
> 


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

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