Dmitry helped me identify the root cause of my problem. The parameters were bound to a FLASH persisted property hence they lost their initial values after first use. I just made them CLIENT and (appart from the long client state request payload) that issue is resolved satisfactorily.
John ----- Original Message ----- From: Lance Java To: Tapestry users Sent: Saturday, December 07, 2013 8:04 AM Subject: Re: component paramter frustrations Perhaps you could write your own persistance strategy. @Persist(MyPersistConstants.EVENT_CONTEXT) Which implicitly appends to the actionlink / eventlink context clientside and updates the fields serverside before delegating to the event.
