I'd have a single onActivate(EventContext context) method instead of two.
On Wed, 27 Jul 2011 15:45:16 -0300, George Christman
<gchrist...@cardaddy.com> wrote:
does anybody see anything wrong with doing something like this
Previous Page
<t:PageLink page="purchase_request" context="new"/>
New PurchaseRequest class.
Object onActivate(String newPr) {
if("new".equalsIgnoreCase(newPr)) {
purchaseRequestState.setPurchaseRequest(new
PurchaseRequest());
return Purchase_RequestIndex.class;
}
return null;
}
void onActivate() {
if(purchaseRequestState.getPurchaseRequest() == null) {
purchaseRequestState.setPurchaseRequest(new
PurchaseRequest());
}
}
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Saving-using-form-zone-tp4639355p4639844.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
Consultor, desenvolvedor e instrutor em Java, Tapestry e Hibernate
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
