i will look at it to see if i can extract the version manager from the Page as its own global thing. Only one thing come to my mind that could be hard.. Keeping the current AccessStack also an option. Because the global version manager for pages should then be integrated into the SessionStore (else we get 2 separate things that are sort of do the same and do have relations to each other.)
So i am thinking of then adding another method besides this on to ISessionStore: IPageMap createPageMap(String name, Session session); also IPageVersionManger createVersionManager(); So that the ISessionStore is the "global" thing. I only then have to see how to get the AccessStackPageStore/Map also right again.. aarghh i just think about something... A changeset of the version manager.. will hold components (that are removed) But those components will always have the parent, because if you remove them then the parent is still references (so that you can call reattach() for example) But this means that when you save only a changeset to disk.. you will save the complete page anyway :( This will be really hard to solve.. (we need the parent for things and besides that if developers hold references to what every, through anonymous classes by accident or by choice that point to a parent or the page..) johan On 1/9/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
I created issue http://issues.apache.org/jira/browse/WICKET-201. Eelco
