>
> But IComponentBorder will do all that for you...
>
> -Clay
>
> -Original Message-
> From: Johan Compagner [mailto:[EMAIL PROTECTED]
> Sent: Saturday, November 10, 2007 5:42 AM
> To: users@wicket.apache.org
> Subject: Re: How to migrate onAfterRender/onBeforeRender
rom: Johan Compagner [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 10, 2007 5:42 AM
To: users@wicket.apache.org
Subject: Re: How to migrate onAfterRender/onBeforeRender from wicket
1.2.6 to 1.3
seee IComponentBorder
On Nov 10, 2007 1:55 AM, rtow <[EMAIL PROTECTED]> wrote:
>
> Big
seee IComponentBorder
On Nov 10, 2007 1:55 AM, rtow <[EMAIL PROTECTED]> wrote:
>
> Big thanks! The onComponentTag(tag) is the perfect replacement for
> onBeforeRender(). Do you have suggestion for onAfterRender()? I
> explained
> that I also have a problem to render onAfterRender() in previous
Big thanks! The onComponentTag(tag) is the perfect replacement for
onBeforeRender(). Do you have suggestion for onAfterRender()? I explained
that I also have a problem to render onAfterRender() in previous mail.
rtow
Johan Compagner wrote:
>
> hmm thats the first case that i see that used
hmm thats the first case that i see that used the onBeforeRender like that.
But what you want is a border around the component see IComponentBorder
or override the onComponentTag(tag);
that is also called right before the tag is rendered.
johan
On Nov 10, 2007 12:35 AM, rtow <[EMAIL PROTECTED]>
