I will add a JIRA then :)
Concerning the zone ajax issue:
I am returning zone.getBody()
Give it try, you will see that with jquery you get the same behavior.
Maybe it’s by design, but I think it’s a bug of the core js stack the function
ElementWrapper.update
adds nested div one after the
A while back I stopped returning Zone, or its body, preferring to use
AjaxResponseRenderer#addRender instead. So I'm curious - do you see the same
effect if you use AjaxResponseRenderer#addRender?
On 24 Jun 2014, at 7:34 pm, Numa Schmeder n...@dfacto.ch wrote:
I will add a JIRA then :)
On Tue, 24 Jun 2014 06:34:25 -0300, Numa Schmeder n...@dfacto.ch wrote:
Also the zone id shouldn’t change on subsequent request… As you have
seen each nested div has a different zone id.
Use Zone's id parameter and that won't happen.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and
Hi,
I'm decorating the RequestExceptionHandler in order to handle exceptions and
then redirecting to the previous page (the one I find in the Referer HTTP
header).
This works fine for normal page requests but I would like to handle also the
case of Ajax requests. The JavaDoc of
It figures that after I sent the email I would find a way to fix it. :-)
I saw that the url that was getting requested had the word 'unauthenticated
http://localhost:8080/etss/login/unauthenticated' added to it, and the
response, for some reason, was the first asset listed in the Layout.
