Just further to this, I've decided not to use BeanEditForm because:
a) I can't set the context - I'd like to use the Id as context so that I
can load the edited bean during 'prepare'
b) The 'async' parameter is not exposed meaning I have to specify a zone
which is not suitable
I suggest these upgrades are considered
On 29/10/2015 12:47 PM, Paul Stanton wrote:
According to jumpstart (no mention in tapestry doc) beaneditform
auto-hides the id field:
http://jumpstart.doublenegative.com.au/jumpstart7/examples/input/edit1/1
*But where is Person's |id| property?* BeanEditForm automatically
hides properties annotated with |@Id|.
From the 'view source' of the jumpstart page, I'm guessing
BeanEditForm is creating a hidden field for the id, not just hiding it
as per @NonVisual
This is not working for me.
Can someone point me to the rules for this feature?
Thanks, Paul.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
