You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Juergen Donnerstag <ju...@gmail.com> on 2010/12/26 14:19:10 UTC
setResponsePage in Component constructor
Hi,
quick question. I have an 1.4 app which uses
setResponsePage(getApplication().getHomePage()); in a Component's
contructor and it works even if the Component is not yet fully
configured (not all children created and added). In 1.5 the same page
throws a MarkupException. In 1.5 Pages obviously are allways rendered,
even with the response page re-set to something else. Is that by
purpose? Why does it make sense to still render the page?
-Juergen
Re: setResponsePage in Component constructor
Posted by Juergen Donnerstag <ju...@gmail.com>.
RestartResponseException works as well, that is correct. However I
wonder if its expected behavior in 1.5 that setResponsePage() no
longer works as in 1.4.
-Juergen
>On Sun, Dec 26, 2010 at 7:40 PM, Clint Checketts <ch...@gmail.com> wrote:
> If you want processing to stop and not render the page wouldn't it make more
> sent to throw a RestartResponseException(getApplication().getHomePage())?
>
> I realize that I'm not directly answering your question regarding
> MarkupException or rendering pages, but figured I'd help where I could.
>
> -Clint
>
> On Sun, Dec 26, 2010 at 7:19 AM, Juergen Donnerstag <
> juergen.donnerstag@gmail.com> wrote:
>
>> Hi,
>>
>> quick question. I have an 1.4 app which uses
>> setResponsePage(getApplication().getHomePage()); in a Component's
>> contructor and it works even if the Component is not yet fully
>> configured (not all children created and added). In 1.5 the same page
>> throws a MarkupException. In 1.5 Pages obviously are allways rendered,
>> even with the response page re-set to something else. Is that by
>> purpose? Why does it make sense to still render the page?
>>
>> -Juergen
>>
>
Re: setResponsePage in Component constructor
Posted by Clint Checketts <ch...@gmail.com>.
If you want processing to stop and not render the page wouldn't it make more
sent to throw a RestartResponseException(getApplication().getHomePage())?
I realize that I'm not directly answering your question regarding
MarkupException or rendering pages, but figured I'd help where I could.
-Clint
On Sun, Dec 26, 2010 at 7:19 AM, Juergen Donnerstag <
juergen.donnerstag@gmail.com> wrote:
> Hi,
>
> quick question. I have an 1.4 app which uses
> setResponsePage(getApplication().getHomePage()); in a Component's
> contructor and it works even if the Component is not yet fully
> configured (not all children created and added). In 1.5 the same page
> throws a MarkupException. In 1.5 Pages obviously are allways rendered,
> even with the response page re-set to something else. Is that by
> purpose? Why does it make sense to still render the page?
>
> -Juergen
>