On Sat, 12 Jun 2010 16:41:56 -0300, Pierce Wetter <pie...@paceap.com>
wrote:
Well, despite your reservations it seems to be working. Perhaps the
other modules are loaded before the app module so that
contributeComponentClassResolver gets called after the one for
AppModule. Looking at the log...
That's why adding a 'core' module is a bad thing: it relies in the module
loading ordering when no promise of this kind is made.
<t:pace.foo />
Must be turned into:
<span t:type="pace/foo" />
because t:type="pace.foo" won't work. Did I do something wrong, or is
that a known issue?
This is working as expected and documented.
--
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
