> 2. Never use onActivate with a parameter
Why not? What about onActivate(EventContext context)? It's always invoked,
no matter how many activation context values is passed, and you have
TypeCoercer-backed coercions for free.
In general I never use onActivate at all. I try and define my page interface
completely with @PageActivationContext and @ActivationRequestParameter. I
also created @Connect which allows me to connect various page fields and I
use that to initialize things. I've found this gives me a very consistent
page interface and allows me to figure out what it is when using Plastic.
This allows me to do things like
@SessionState
@Property
private CartSession cartSession;
@Property
@Connect("cartSession.items")
private List<OrderItem> items;
Don't worry CartSession is really stored in AWS DynamoDB not the session.
and
public class RowNew {
@ReplaceBreadCrumb(RowEdit.class)
Object onSuccess() {
return row;
}
Which modifies my breadcrumb trail and causes the method return to the Edit
page with the correct arguments.
I can also dynamically generate documentation for each page and how to call
it. I can't help it I used ACS openacs.org before Tapestry.
> 6. Always use BeanEditForm
I never use BeanEditForm, but I do use BeanEditor a lot. :)
I can see that. I have a few hacks to make BeanEditForm work for me.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Pagelink-above-grid-picks-up-context-from-last-pagelink-in-grid-tp5660049p5664809.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
