In 2.0 the code has been completely reworked. Very simplistic: In 1.x
we iterate over the markup, search the component, and render the
component based on the current markup position. This approach works
well for Pages (none-ajax components) but has some shortcomings when
it come to per-component render (ajax). In 1.x we use
MarkupFragmentFinder to find the markup per component, but since
finding a component for given markup is not a simple process (see
Resolvers), it is even harder to define the invers function in
MarkupFragmentFinder. In 2.0 we changed it completely to a
MarkupFragmentFinder approach (kind of) which means there is no more
difference between a std Page render process and an ajax render
process. This (large) change has not yet been backported to 1.3.

Juergen




On 5/7/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
Normally if you want to repaint a repeater then you have to repaint a parent
of the repeater

But there is some changes in the markupfinding code so juergen do you know
what is different?

johan


On 5/7/07, Jan Vermeulen <[EMAIL PROTECTED]> wrote:
>
>
> When using an AjaxRequestTarget to render a component, it calls
> Component:renderComponent() to do the actual rendering.
>
> In the former 2.0, that component could be a component that has no own
> markup (because it was generated by a repeater).
>
> In the current thrunk, using an AjaxRequestTarget to render such a
> component
> fails, because Component.renderComponent() uses a MarkupFragmentFinder to
> find the markup for the component,
> and that MarkupFragmentFinder throws an exception because it did not find
> any markup with the id of the component (which does not exist, since the
> component has been generated dynamically).
>
> Is this no longer possible in Wicket ? It was working fine in 2.0, and
> allowed us to do ajax refresh of dynamic content of tables or menus.
>
> Jan.
> --
> View this message in context:
> 
http://www.nabble.com/Backporting-from-2.0%3A-renderComponent%28%29-fails-if-there-is-no-markup-tf3703472.html#a10356568
> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>
>

Reply via email to