I'm looking forward to this implementation.
The best I can offer is to help test. Please post a message to inform
me when you are tackling this. Otherwise where can I latch on?
On 08/07/06, Jesse Kuhnert <jkuhnert@gmai...> wrote:
> To really do something like this properly you'd probably have to mess around
> with the internal implementations of FormSupport / AbstractFormComponent in
> order to skip over rewinding of form components that you don't want
> validated / values parsed from.
> This also starts to slide into the world of direct rendering / etc. Not an
> easy thing to do currently. I plan on implementing this in 4.1, but will
> probably save it for last as I'm assuming I'll need lots of time to play as
> it'll probably be as hard to implement as adding the new render cycle was.
> (Not that it was hard to do because of tapestry, just hard to do in a clean
> / intuitive / non-breaking way that makes sense for the API . )