On Wed, 24 Aug 2011 14:49:36 -0300, Lenny Primak <[email protected]>
wrote:
I think the key here at least for me is that there is one entry point
for most common things.
Then there's a problem: defining what is the most common things.
@Inject is nice but tapestry also has @Contribute and other inject
variants.
@Contribute is not used for injection at all. There's @Inject (used in at
least 99% of the time) and @InjectService (very seldomly used).
@InjectComponent, @InjectContainer are not related to dependency injection
at all.
I for one am having to constantly field questions on how do I do this
and it's usually a question of doing an inject. The API will prevent
those questions from happening in the first place.
How would this API look like? What API you would use as inspiration? There
isn't a single definition of API nor just one way of architecting one.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
