Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
Received-SPF: pass (herse.apache.org: domain of
 the.mindstorm.mailinglist@gmail.com designates 64.233.182.187 as permitted
 sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=s5ERz83kcv9lEjcoGPyEf8veFmPK/+nTq9iJxHHqWnJQH5pb/D1UYzSddahlCv0wgaerW9PA2Ew3bs5ZsN2DvOXpGxcU4hoOr72TdURwjl+4nZPI0IrLHKm0VlRbSECqGzWfhMQfsSWoIHa0/y9VOqQtj1OuIHDMurGxzDoq0FQ=
Message-ID: <c6f400460702260916o23b6fc81ta87e5213c2140001@mail.gmail.com>
Date: Mon, 26 Feb 2007 19:16:13 +0200
From: "Alexandru Popescu" <the.mindstorm.mailinglist@gmail.com>
To: "Struts Developers List" <dev@struts.apache.org>
Subject: Re: Guice 1.0rc2
In-Reply-To: <a74683f90702260830g51b6e05dme8ff7f9b7171eefd@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <a74683f90702260707ic9a0b82yd57bfd84c4450479@mail.gmail.com>
	 <690806.24784.qm@web54306.mail.yahoo.com>
	 <a74683f90702260830g51b6e05dme8ff7f9b7171eefd@mail.gmail.com>

On 2/26/07, Bob Lee <crazybob@crazybob.org> wrote:
> On 2/26/07, Konstantin Priblouda <kpriblouda@yahoo.com> wrote:
> >
> > Hi Bob,
> > I'd like to say that I'm codeveloper of
> > pico/nanocontainer.
>
>
> I've used Pico and Nano. Nano uses my AOP framework. You should try Guice.
>
> > What's important is that you don't depend on the
> > > implementation. Depending
> > > on the interface and annotation is OK. Strings are a
> > > pain.
> >
> > We do not depend on string keys to dientify components
> > - key in container  is just object, and is
> > needed only in case of ambiguity ( but it could be
> > string as well )
>
>
> Using these key objects is more verbose than using annotations with Guice.
>
>
> > Basically I just register this session component -
> > and my HibernateUserManager receives it in
> > constructor.
> >
> > Why do I need an annotation to achieve this?
>
>
> The annotation indicates which constructor you want injected (to the
> framework as well as other programmers). What happens if you forget to
> configure a PasswordHasher in Pico? No hashing? That's not very secure.
>
> If you can't annotate a constructor (because you don't control the code),
> you can use a custom provider. For example:
>
> class HibernateUserManagerProvider implements Provider<HibernateUserManager>
> {
>   @Inject Session session;
>   @Inject PasswordHasher passwordHasher;
>   public HibernateUserManager get() {
>     return new HibernateUserManager(session, passwordHasher);
>   }
> }
>
> Well, there is still a question why it is better than
> > pico ;)
>
>
> Write less code, and get better up front checking and better performance.
> What more do you want?
>
> Bob
>

Bob it sounds cool, but without documentation I would say that there
are not many chances people will look into it. I will wait for the
moment the documentation becomes available.

./alex
--
.w( the_mindstorm )p.

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