Why couldn't you parse for wicket:param prior to the actual rendering phase? That is, markup-side rendering occurs before Java-side rendering or something along those lines. Maybe that'll help overcome issue #1? Just a guess...

Gili

Juergen Donnerstag wrote:
I did some further investigation on the wicket:param stuff.
Unfortunately I don't have good news. There are some problems which
I'm not able to solve and which significantly limit the usability of
wicket:param. I'll try to explain it. A "common" request has been to
be able to set the number of rows a ListView will display in markup.
<wicket:param rowsPerPage="10"/> following the <table> tag (or any
other tag which is associated with the ListView) was meant to do
exactly that. That is the requirement. Taking a closer look at Wicket,
what happens internally and what other constraint are there:

1) you can not modify the component tree while in rendering state. The
reasons are out of scope for this discussion. Take it as a fact. The
only exception is autoAdd() which is used e.g. for autolink components
which are added to the component tree at render time. Because
autoAdd() is causing issues with our js + css support, autoAdd is not
likely to survive for very long. We need to find another solution.

2) Because of 1, a ListView is populated during
internalOnBeginnRequest(), which is called prior to the render phase.
It is important to know that, because it is prior to the render phase,
the associated markup is not yet know. It has not yet been read. Thus
neither the <table> nor the <wicket:param> tag is available. Thus you
can not use it to set the number of rows per page. And because of 1,
you can not change (remove, add, replace) the number of rows as you
would change the component tree.

Trying to think about other uses for wicket:param, I guess most of
them will face a similar problem: The information (e.g. rowsPerPage)
available earliest in the render phase, during which changes to model
and component tree are no allowed.

Sorry that I don't have better news. Any ideas on how to overcome that problem?

Juergen


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop


--
http://www.desktopbeautifier.com/


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to