Mailing-List: contact beehive-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Beehive Users" <beehive-user@incubator.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of kentaminator@gmail.com
 designates 64.233.162.199 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=hm8Tp2GB0VxdT9eA4BOK+BLhrduXFQNFwCTAEiPnd+WcvlZjq/1pqTJMT0N3jjToeGLjY9xRigiTxEZQhVUT06NQJ7NKTPhPoVd7bgE+menYdtepHKefDtKmgX5v5tj9wwCcpoi31P97xjncy0FcnrLZTbJIkEc3c6d1XySsTgA=
Message-ID: <e52f74f805081608081093a6eb@mail.gmail.com>
Date: Tue, 16 Aug 2005 08:08:20 -0700
From: Kenneth Tam <kentaminator@gmail.com>
To: Beehive Users <beehive-user@incubator.apache.org>
Subject: Re: Control: annotation based injection
In-Reply-To: <b60d154305081203065b7d1506@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <b60d154305081203065b7d1506@mail.gmail.com>

Hi Antony,

Can you provide some more detail on the scenario you're interested in?

You can think of controls as JavaBeans with a variable amount of
"container" provided functionality.  As such, using them can be as
simple as instantiating a JavaBean via existing JavaBean instantiation
mechanisms such as java.beans.Beans.instantiate or <jsp:useBean>.  The
controls model provides more "advanced" instantiation APIs in
org.apache.beehive.controls.api.bean.Controls (for example, this
allows explicit setting of initial properties and the container
context).  Any Java file/class can also participate in declarative
controls initialization, where you simply annotate a field whose type
is a control or a control interface with @Control -- when such a file
is processed with APT, a helper class is created with a single method
that knows how to inject all the controls in the original client.  One
of the first features that control containers typically provide is
support for automatically calling that helper; that's what allows e.g.
controls, pageflows and Beehive webservices to support
@Control-annotated fields seamlessly to the user.

The other major feature that control containers provide is context
management; not all controls need this, but features like control
lifecycle callbacks, external property override, etc, don't work
without it.  Beehive comes with a servlet filter that provides such
container services -- this means any webapp code can be
controls-enabled simply by adding a filter to web.xml.  See
org.apache.beehive.controls.runtime.servlet.ControlFilter.

hope this helps,
k


On 8/12/05, Antony Chien <antony.chien@gmail.com> wrote:
> Hello everybody:
> I'm quite interested in the feature that beehive provides, especially the
> annotation based dependency injection.
> However, how do I make sure that this feature is available wherever I wan=
t?
> I mean, can I just take a POJO and add an annotation to call a Control? I=
s
> that possible?
> If not, then how do I prepare a right environment?
>=20
> --
> Regards,
> Antony Chien
>=20
>