On Tue, Jun 2, 2009 at 3:13 AM, Moritz Gmelin wrote:
> Hi,
Hi!
> back to my original question: Is this NPE a bug in T5.1 or is redirection
> not working at all?
You shouldn't do redirection that way, but a NPE inside Tapestry code
surely looks like a bug.
--
Thiago
--
Hi,
back to my original question: Is this NPE a bug in T5.1 or is
redirection not working at all?
M.
Am 01.06.2009 um 23:31 schrieb Thiago H. de Paula Figueiredo:
Em Mon, 01 Jun 2009 18:23:04 -0300, Moritz Gmelin > escreveu:
Thanks for this try,
Ooops, my mistake. You can return a Clas
Em Mon, 01 Jun 2009 18:23:04 -0300, Moritz Gmelin
escreveu:
Thanks for this try,
Ooops, my mistake. You can return a Class or page instance only in
onActivate().
Try
public Class onActivate()
{
if (needsToRedirec
Thanks for this try,
but
@BeginRender
public Class beginRender()
{
return Start.class;
}
gives another Exception
org.apache.tapestry5.internal.services.RenderQueueException: Render
queue error in Begin
Em Mon, 01 Jun 2009 17:49:40 -0300, Moritz Gmelin
escreveu:
Hi,
Hi!
You could just return Page1.class in beforeRender() or onActivate() to
redirect instead of injecting Response and return null to continue
processing the page without any redirection. This works in any Tapestry
versio
Hi,
we just tried porting a larger application from 5.0.18 to 5.1.0.5.
One thing is causing troubles though. We use redirection in some cases
to bring the user back to the start page if an error occurs.
This is how we do it in T5.1 (code from a sample Page to reproduce the
NPE in a clean
