On Fri, 18 Jun 2010 16:49:46 -0300, Robert Hailey <rob...@cmediacorp.com>
wrote:
Really? Surely there is a difference somewhere!
Here is my (basic) understanding so far:
tapestry-filter:
creates a ioc-registry
(it already contains the base-ioc services)
it adds the tapestry services
it adds (or knows-the-path-to) the services from "app.services.*"
The above line isn't correct. Tapestry services are defined in
TapestryModule and TapestryInternalModule, Tapestry-IoC modules classes as
any other.
The base IoC services are a module class as any other, except that they
are automatically loaded. No special handling.
So is it the case that tapestry-hibernate-*.jar presence in the web-app
folder is what ultimately prompts it's registration?
Yes. The same happens to any JAR in the classpath, as long as it has the
correct entries in their manifest files.
--
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
