Are there any plans for backporting this ?
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#a10370932
Sent from the Wicket - Dev mailing list archive at Nabble.com.
It'll take some time. It was not an easy thing to do and the some
details of the approach we took needs to be reworked. But we'll get
there. Not sure it'll make it into 1.3 though.
Juergen
On 5/8/07, Jan Vermeulen [EMAIL PROTECTED] wrote:
Are there any plans for backporting this ?
Jan.
--
It would be good to open up a JIRA issue for that if you plan to work
on that, Juergen.
Cheers,
Eelco
On 5/8/07, Juergen Donnerstag [EMAIL PROTECTED] wrote:
It'll take some time. It was not an easy thing to do and the some
details of the approach we took needs to be reworked. But we'll get
Thanks. I'll fix it on our side for the moment.
I will keep reporting things I come across while backporting. Hope it's not
only harrassing on the core developers. Somehow I try to contribute by
pointing out possible bugs or missing things.
Jan.
--
View this message in context:
Thanks. I'll fix it on our side for the moment.
I will keep reporting things I come across while backporting. Hope it's not
only harrassing on the core developers. Somehow I try to contribute by
pointing out possible bugs or missing things.
Please keep on harrassing. That's the way we keep
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
Johan Compagner wrote:
Normally if you want to repaint a repeater then you have to repaint a
parent
of the repeater
You didn't have to in the former 2.0. And I don't see any good reason why
you would not be allowed to rerender a component that has no markup. We used
it (with the former
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
