IMarkupFragment

[Juergen Donnerstag]

I just committed IMarkupFragment to 1.5 trunk. Via
Component.getMarkup() is allows you to get the component's associated
markup virtually anytime. No need to wait for the render process any
more. This feature is added only, meaning it by default it is used to
get the markup fragment during Component.renderXXX() and it throws an
exception if unable to find the markup but the fragment is not yet
used for rendering.

This default behavior can be disabled by subclassing
Application.isMarkupFragmentEnabled(). Though it is already more
stable than I thought it would be, there are certainly many apps with
their own components which don't yet work.

Juergen

[martin-g]

Hi Juergen,

I see SVN conflicts in org/apache/wicket/markup/Markup.java committed.
They are in the comments though.

El jue, 17-09-2009 a las 07:46 +0200, Juergen Donnerstag escribió:

> I just committed IMarkupFragment to 1.5 trunk. Via
> Component.getMarkup() is allows you to get the component's associated
> markup virtually anytime. No need to wait for the render process any
> more. This feature is added only, meaning it by default it is used to
> get the markup fragment during Component.renderXXX() and it throws an
> exception if unable to find the markup but the fragment is not yet
> used for rendering.
>
> This default behavior can be disabled by subclassing
> Application.isMarkupFragmentEnabled(). Though it is already more
> stable than I thought it would be, there are certainly many apps with
> their own components which don't yet work.
>
> Juergen
>

[Juergen Donnerstag]

Thanks. I'll fix it.

Juergen

On Thu, Sep 17, 2009 at 8:49 AM, Martin Grigorov <mcgregory@...> wrote:

> Hi Juergen,
>
> I see SVN conflicts in org/apache/wicket/markup/Markup.java committed.
> They are in the comments though.
>
> El jue, 17-09-2009 a las 07:46 +0200, Juergen Donnerstag escribió:
>> I just committed IMarkupFragment to 1.5 trunk. Via
>> Component.getMarkup() is allows you to get the component's associated
>> markup virtually anytime. No need to wait for the render process any
>> more. This feature is added only, meaning it by default it is used to
>> get the markup fragment during Component.renderXXX() and it throws an
>> exception if unable to find the markup but the fragment is not yet
>> used for rendering.
>>
>> This default behavior can be disabled by subclassing
>> Application.isMarkupFragmentEnabled(). Though it is already more
>> stable than I thought it would be, there are certainly many apps with
>> their own components which don't yet work.
>>
>> Juergen
>>
>
>