. I tried to add a
>>>> Persist
>>>> >> boolean and set it to true in the onSuccess method and included an
>>>> >> if-else in the template to render the appropriate piece. If I just
>>>> used
>>>> >> @Persist, I could
e template to render the appropriate piece. If I just
>>> used
>>> >> @Persist, I couldn't get back to the form to ever load again once it
>>> was
>>> >> submitted the first time. If I used @
gt; was
>> >> submitted the first time. If I used @Persist("flash"), I could reload
>> >> the form on demand, but now the grid pager links would take me back to
>> >> the form (since the boolean w
once it was
> >> submitted the first time. If I used @Persist("flash"), I could reload
> >> the form on demand, but now the grid pager links would take me back to
> >> the form (since the boolean would reset to false).
> >>
> >> Does anyone
eset to false).
>>
>> Does anyone else combine their forms and response pages? Is this a bad
>> practice? It just seems silly to have to keep track of 4 entities for a
>> simple form/response. Boy do I miss Perl.
>>
>
>
-
).
>
> Does anyone else combine their forms and response pages? Is this a bad
> practice? It just seems silly to have to keep track of 4 entities for a
> simple form/response. Boy do I miss Perl.
>
--
View this message in context:
http://www.nabble.com/-T5--Combine-a-form-and-respo
rl.
--
View this message in context:
http://www.nabble.com/Combine-a-form-and-response-in-same-template-Java-class-tp20287170p20287170.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-ma
