On Mon, 17 Mar 2014 12:31:31 -0300, George Christman
<gchrist...@cardaddy.com> wrote:
Hi Thiago, I'm aware the hibernate piece is unrelated, however what I'm
asking is storing my object in the user session the correct approach?
I wouldn't say it's the ideal solution, but I'd consider it a valid one.
I'm really wondering if I'm using Tapestry properly to produce warnings.
As someone already said, wrap the form inside a Zone, have your form
update this zone. Use the Errors component to show the validation errors.
That's what I'd do.
I don't want to just patch the issue with hibernate .merge if I'm not
doing
something correctly with Tapestry first.
Session.merge() is actually more recommended than saveOrUpdate() anyway. I
learned this the hard way. merge() completely solves the "a different
object with the same identifier value was already associated with the
session" problem.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
