> Does Tap3 have a hook for this sort of functionality? Or is this a _bad > thing_ > for reasons I'm too much of a newbie to understand?
I am also having issues with persistent properties. They simplify a lot of things but sometimes they are too persistent :) A pattern that are reoccurring in my webapps is this: 1. A page (for example a page with a list of objects) sets an object property on another page (for example an update-page) and returns it from a listener method so that it is displayed to the user. 2. The second page contains a form which the user uses to update properties on the object 3. The user hits "Submit" and the object is saved to the database. Doing this with hibernate is really simple but if the user decides to hit a pagelink on the border-component of the site instead of hitting submit or cancel on the form, the persistent page property is "leaked". It is still in the session even though it doesn't need to be there. I could convert all the pagelinks to directlinks and have listener-methods that clear the page-properties but that just seems to be plain wrong, I don't want to litter my pages with methods like those. I could also implement some kind of scheme where all the properties of the object are mapped to fields in the form so that they are transferred from page to page but there might be sensitive data like passwords that I want to keep strictly on the server (these could get lost without persistent page properties). I could also implement some kind of scheme where an id is passed around and the object gets re-fetched from the database on every page reload but that seems so php-ish. I guess James have a similar problem but what is the solution? I have a nagging feeling that the solution is simple but I have yet to find one. Please enlighten me... Thanks Gabriel Falkenberg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
