On Jun 12, 2010, at 1:08 PM, Thiago H. de Paula Figueiredo wrote: > 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.
Well, SubModules are always loaded second it seems. But I suppose you can't rely on the auto loading order. But I think there should be a mechanism for overriding core components, even if you had to do each one explicitly. For instance, it would be a great and wonderful thing if someone made a drop in replacement for Grid that used the ExtJS stuff. > >> <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. Ok, good to know. pierce --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
