That's sad. I definitely prefer the "least greediest constructor"
approach myself. But at least the annotation will be a java standard,
so I don't have to create dependencies on Guice in my code to harness
it as an implementation.
I think T5 being looser in its constraints on one's code should mean
that it could bind JSR330-friendly components, but wouldn't have to
require the annotation in order to bind unambiguous cases.
Christian.
On Oct 27, 2009, at 4:43 PM, Thiago H. de Paula Figueiredo wrote:
Em Tue, 27 Oct 2009 18:21:06 -0200, Howard Lewis Ship <[email protected]
> escreveu:
I haven't reviewed what the spec even is. Hopefully Bob "You're
obviously not as committed to DI as I am" Lee didn't create something
totally at odds with T5 IoC.
The approved JSR 330 version is the one that only provides
annotations, not the configuration API, so I guess the probability
of a clash with T5-IoC is small. A single point I can recall is that
330 requires an annotation for injection to work, while T5-IoC
doesn't. Besides that, most concepts are very similar. 330 was
inspired by Guice, an so was Tapestry.
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
