The implementation of ComponentEventLinkEncoder is only examining the
requested path.
http://tapestry.apache.org/tapestry5.1/apidocs/org/apache/tapestry5/services/Request.html#getPath%28%29
Since event context and page activation context are encoded into the patn
it works fine. Form inputs are never incoded into the path.
Is it your question?
On Oct 22, 2009 4:02pm, Stephan Windmüller
<stephan.windmuel...@cs.tu-dortmund.de> wrote:
Stephan Windmüller wrote:
>> The Request object still contains the URL with the needed path. How do
I
>> get the eventContext from here?
> The solution for this was the service "ComponentEventLinkEncoder". It
> creates a PageRenderRequestParameters object which contains the
> EventContext. Thanks to Igor Drobiazko for pointing this out!
Hm, this does not work with forms. Is the POST data not part of the
Request?
- Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
