I think the concept of rendering a whole page as one continues process
has to go anyway. Each component should be able to render just itself,
and the rendering of the page is just rendering all the components.
Juergen, are you reading with us? Would this be hard to implement (or
can we do this allready)?
As for the models, as long as we have an observer pattern implemented,
it is up to the model implementation how and when observers should be
notified.
Eelco
Johan Compagner wrote:
most db driven models don't know if they are dirty or not
For this kind of thing the developer itself can say invalidate
youreself (the component or maybe say it to the model) and render again.
Because i know or think you are changed.
You also have non db models (the non detachable once) and that one can
set the dirty flag by firing a property change where the components
who has
that model are setting the dirty flag)
then the question is should there be some automatic part where wicket
as a framework guesses now it is time to do the complete page render
or this component (that is backup by a database/detachable model) render.
johan
-------------------------------------------------------
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-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
