On Wed, 25 Apr 2012 02:07:55 -0300, netdawg <net.d...@yahoo.com> wrote:
THIAGO: return person.getId() breaks the Edit Page completely with Render
queue error in BeginRender...
Full stack trace please.
Fully qualifying the Edit link, as below, works fine to get the Edit
page to render as Create (edit/) ...without filling the last record as
(edit/5)
<t:pagelink page="person/EditPerson">Create NEW Person/Advanced
Search</t:pagelink>
Have you tried <t:pagelink page="person/EditPerson" context="null">Create
NEW Person/Advanced
Search</t:pagelink>
Page re-use seems fraught with session/objects management issues.
I still don't think so. Use the activation context (and passivate) and you
won't have problems.
In any case, this is all looking like Struts, only a bit
backwards...Create,
Edit and QBE pages are all identical except for the ACTION of the submit
button. In Struts, you just send the action to a different METHOD in the
same CRUD class - if it needs something in the Valuestack it will get it
otherwise it just proceed merrily along.
You can use EventLink instead of PageLink for this kind of scenario.
But due to apparent ambiguity of activate/passivate in Create/Edit,
What ambiguity?
I would be happy to be proved wrong - if there is a working app out there
which does all three Create/Update and QBE...
I usually have one page for creating and updating and another for searches.
--
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
