On Wed, 15 May 2013 17:06:13 -0300, Lenny Primak <lpri...@hope.nyc.ny.us>
wrote:
Now saying that, I am not saying Tapestry, or Tapestry-IOC sucks, I just
feel Tapestry-IOC is unnecessary in the current technology landscape and
presents a barrier to learning Tapestry.
Tapestry-IoC is very necessary for Tapestry. Tapestry needs distributed
configuration. CDI, as far as I know, doesn't provide that. Spring doesn't
too, otherwise Tapestry would have used it instead of creating another IoC
framework. JSR 330 (Dependency Injection for Java) also doesn't. I posted
a ticket asking for distributed configuration on the JSR, but the guys
said you could do that by creating another service that receives the
contributions, but then you end up with your service and another service
just for configuring it. And replacing Tapestry-IoC for another IoC
framework won't prevent Tapestry newbies from learning an IoC framework.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
