> this is because the parent markup isn't being reloaded when the child > changes?
Yes. If the base markup (not the derived markup) is stale, the "merged" markup assoicated with the component is not reloaded. If the directly associated markup is stale, it will be reloaded including the base classes markup. > Can't we link those in the cache? So that when the child changes it > fires this to the parent(s)? > They are in the cache, but we return a merged markup stream. Not sure it is clear: the original markup (list of markup element) loaded from file gets *replaced* by the a markup which has been merged from the extended and the base classes markup. The "new" markup does not have even have a clue that is has been merged and what the sources were. What we need is something that invalidates all markup in the cache which depends on the base markup. This is different to our current approach, where there is a one-to-one relationship between component and markup. I'll think about it. > What method do you prefer? > Currently the new one, because it is easier to understand. It is not twisting my head like the current one. 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
