On 12/22/2010 01:44 PM, Thiago H. de Paula Figueiredo wrote:
On Wed, 22 Dec 2010 16:05:15 -0200, Rich M <rich...@moremagic.com> wrote:
Hmm, I'd tried that several ways, every time the ParameterNames()
list was empty and I couldn't fetch the parameter I was looking for.
I tried peeking the Request parameters in the Event method as well as
@SetupRender.
Are you sure you added the query parameters to the URL generated by
ComponentResources.create*EventLink() using JavaScript? Or at least
you added this values as hidden fields?
I suppose this is where I am confused. I currently use JavaScript to
write the query parameter into the activation context of the EventLink.
This is what is very messy as described before. The query parameter is
pulled from the hidden input field in the enclosing form. The javascript
method setupSubmit takes care of converting the value of the hidden
input field into the activation context of the URL for the EventLink.
The one with the "productsList" id will have the query parameter in its
value attribute.
There was an additional complication with submitting the HTML form
and the EventLink at the same time.
Why would you do both at the same time?
My logic was that the EventLink triggers the Event Handler method, while
the form submission puts the hidden input into the Request parameters.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
