given a particular problem in versioning and some anticipation of a horde of other problems, i think we need to change our model for rendering components a little. eelco and maurice verbally agree, but we'd like any feedback from the list too. the versioning problem is that urlFor() can be called during rendering to create a url of version N. if a component further down the page makes a structural change while rendering, it will increase the version at that time, resulting in urls further down the page having version N + 1. the root problem here is one that chris and i wanted to fix some time ago and one that seems worth fixing: once rendering begins, the component hierarchy should be immutable. any attempt to change the structure during rendering would result in an exception. to implement this change, we'll have to change ListView (yet again... sorry juergen!!) so that it has a component building (populate) phase and a render phase which are decoupled. i think this is a really good change, but i could be missing something too... does anyone see any problems with this?
jon
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
