I'm using Tapestry 3.0.3. I have an app where one is presented with a list of items, each of which can be edited in a separated page. If I open 2 items (in my situation using Firefox's tabbed views) in separate pages, there seems to be some "crosstalk" between them, in the sense that doing anything that requires a page reload on the first item will pull in data belonging to the second item. First and second referring to the order in which the pages were opened.
I'm wondering if this is because SessionPageRecorder doesn't distinguish between the data for two instances of the same page (Bearing in mind that pages are stored in a pool, and initialized and detached for each usage etc etc)? And it seems that persistent page properties also do not make this distinction? I can understand that it would be quite difficult to make this distinction in a generic way, but since in my case each view deals with a separate object which has an id, I could use the id to make the distinction. The question then is: what's the best way to do this? A custom PageRecorder? bye John --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
