Sortable: i'd use the contrib.table component group, but that's not a
priority.
Security: an in house approach handled at two levels - firstly page
level, so each request is subjected to a credentials check - and
secondly at controller level so each controller method double checks
that the procedure is being called by the appropriate user with the
appropriate credentials. It's not as standardised as say Acegi, but
simple and effective.
Not sure what you mean re button label. The button either says "Add
Transaction" or "Edit Transaction". There is no confirmation, after
you've clicked the button it's saved.
Loïc Talbot wrote:
Hi Paul,
I've tried it and found that the button label was not changed to "save" when
you edit a transaction (ok, so poor remark for such a work, sorry) :-)
I have used tapestry 4.1.2 for a while and one of the main requirements was
to have a sortable grid where you could also select which row to delete
within the table.
In your transaction list page, is it a big issue ?
May I know what did you use for security layer ? acegi, servlet-filter ?
Loïc
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
