Ah ... that works (as expected). Clarification for me - I know that Tapestry creates "pools" of my pages. Conceptually, I've often wondered how it does that - ie: does it nullify all the fields between requests?
Given this example, is it safe to say that it nullifies or invalidates any field in the components, pages, or mixins package? ... And more to my question - leaves any other declared and instantiated fields alone? For instance, if I instantiate and assign some utility class to a page.field - is it predictably going to persist and even retain values that I might set in it across requests? Thanks Thiago, -Luther On Tue, Mar 3, 2009 at 8:15 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > Em Tue, 03 Mar 2009 23:10:46 -0300, Luther Baker <lutherba...@gmail.com> > escreveu: > > Render queue error in BeforeRenderTemplate[initiative/BlockEdit:sid]: >> Failure reading parameter 'model' of component initiative/BlockEdit:sid: >> Component class >> com.fuzzybearings.notebook.web.pages.initiative.InitiativeLabeler may not be >> instantiated directly. You should use an @InjectPage or @InjectComponent >> annotation instead. >> > > Tapestry loads page, component and mixin classes using a special > classloader that changes them on the fly. That's why you must never, never, > ever put a class or interface that is not a component in the components, > pages, or mixins package. That's also why you cannot instantiate a > component, page or mixin in your package: you must let Tapestry to do that. > > The solution is to move the InitiativeLabeler to another package outside > com.fuzzybearings.notebook.web.pages. > > -- > Thiago H. de Paula Figueiredo > Independent Java consultant, developer, and instructor > http://www.arsmachina.com.br/thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
