[TAPESTRY-1599] Make it possible to differentiate between preparing for a Form render vs. preparing for a Form submission

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.0.5
• Fix Version/s: 5.0.8
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Nick Westgate
• Created: 25/Jun/07 13:07
• Updated: 20/Jan/08 23:15
• Resolved: 20/Jan/08 23:15

Description

(I'm top posting over our previous correspondence below.)

My initial response would be that the optional context parameters signature is
very natural and that prepending a boolean would dilute the current API's clarity.

Do these events need to share the same name? It smacks of the rewind.
(Not to malign what was, at the time, a great idea.)

Cheers,
Nick.

Howard Lewis Ship wrote:
> I could change Form to pass along a boolean indicating whether it was
> for render or for submit. Please add an issue to JIRA.
>
> On 6/22/07, Nick Westgate <[e-mail]> wrote:
>> Hi.
>>
>> Does anyone see a way to differentiate these prepare events?
>> I'm using an ugly hack because I can't find another way.
>>
>> boolean rendering;
>>
>> void setupRender()
>>

{ >> rendering = true; >> }

>>
>> public void onPrepareFromHistoryItemForm(int index)
>> {
>> if (rendering)
>>

{ >> ... >> }

>> }
>>
>> Cheers,
>> Nick.