Re: hide primary key on call to edit form

2012-09-06 Thread Lance Java
Firstly, I would avoid session usage unless it is definitely required.
Passing the primary key in the URL is a good way of avoiding session usage.

Secondly, tapestry is most likely adding the primary key to the URL because:
a) The EditEvent page has an onPassivate() method. 
b) The EditEvent page has a property with a @PageActivationContext
annotation



--
View this message in context: 
http://tapestry.1045711.n5.nabble.com/hide-primary-key-on-call-to-edit-form-tp5716100p5716101.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



Re: hide primary key on call to edit form

2012-09-06 Thread Chris Cureau
You guessed right...I removed the onPassivate() method and all is well.
Thanks!

On Thu, Sep 6, 2012 at 10:36 AM, Lance Java lance.j...@googlemail.comwrote:

 Firstly, I would avoid session usage unless it is definitely required.
 Passing the primary key in the URL is a good way of avoiding session usage.

 Secondly, tapestry is most likely adding the primary key to the URL
 because:
 a) The EditEvent page has an onPassivate() method.
 b) The EditEvent page has a property with a @PageActivationContext
 annotation



 --
 View this message in context:
 http://tapestry.1045711.n5.nabble.com/hide-primary-key-on-call-to-edit-form-tp5716100p5716101.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