On Mon, 13 Aug 2012 16:03:24 -0300, Lenny Primak <lpri...@hope.nyc.ny.us>
wrote:
Also tapestry IOC is supporting and not a primary component of tapestry.
The web framework is the primary.
Yep, but Tapestry-IoC is amazing on its own too. :)
Having worked with tapestry for almost 2 years now I can honestly say
that the biggest hump in learning it was actually tapestry IOC and the
fact that doing everything requires knowing which service to inject. I
would still prefer a universal API so the IDE can suggest what I have to
call instead of trying to figure that what to inject/decorate/advise
etc. with an IOC framework that I have not used before.
For the service discovery part, why don't you create a service that
provides getters for these services that are usually used and make it an
open-source project? It would be nice to see something like that.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
