On Thu, 11 Aug 2011 08:45:44 -0300, nillehammer
<tapestry.nilleham...@winfonet.eu> wrote:
No, that's part of what Tapestry calls "distributed configuration" You
can define separate modules and pack them into separate jars.
Well, my definition of distributed configuration is different: it's the
ability of more than one module class to contribute configuration for a
given service. Spring and Tapestry-IoC have the ability of having
different sources of configuration (modules) and packing them in different
JARs, but only Tapestry-IoC has distributed configuration.
From http://tapestry.apache.org/tapestry-ioc-configuration.html: "One of
the key concepts in Tapestry IoC is distributed configuration. The
distributed part refers to the fact that any module may configure a
service. Distributed configuration is the key feature of Tapestry IoC that
supports extensibility and modularity."
--
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: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
