On Jun 18, 2010, at 3:06 PM, Thiago H. de Paula Figueiredo wrote:
On Fri, 18 Jun 2010 16:49:46 -0300, Robert Hailey <rob...@cmediacorp.com
> wrote:
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.
I see, and once a registry is built it is not possible to add to it.
Is a way for one tapestry module to pragmatically require another (at
registry-build-time) such as providing a class name/instance?
--
Robert Hailey
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
