Hi everyone, sorry about my wording, was very tired and practically bug eye'd by the time I wrote that yesterday. Anyhow, my real world issue is as followed.
When serverside validation occurs and the application returns the page, I'm having an issue with some interface UUID's not being passed to some of the interface elements properly. My proposed solution was to persist the root object to hibernate which would give me real primary keys on page return to work with instead of the originally generated UUID's. I was under the impression that I could persist my object to hibernate only when the form contains validation errors and when the page returns "reloads" I could reattach my form to the session persisted at validation. I was hoping this session would contain all my form data and real id's previously persisted at validation. I did take a look at session.lock, not entirely sure I understand it yet. I hope this better helps to clarify my issue. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-Hibernate-session-reattach-tp5584040p5585820.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
