I don't fully understand your problem... Tapestry doesn't create objects for
you by default (except ASOs)... Page properties are only holders of values.
I'm not sure where you get a second copy of one of your hibernate objects.
Also you should not override equals and hashcode! This might just hid
I find that when things seem awkward in Tapestry it is often because I use
the wrong approach.
If you find yourself forced to create a session when there is no need for
it, you probably need
to rethink how you use listeners/triggers on page/component.
"Vinicius Carvalho" <[EMAIL PROTECTED]> skr
ing this problem, RTFM ;-)
>
>
> Cheers,
> detlef
>
>
>
> -Original Message-
> From: Vinicius Carvalho [mailto:[EMAIL PROTECTED]
> Sent: Montag, 21. August 2006 14:01
> To: Tapestry users
> Subject: Re: Tapestry with Hibernate vs JSF with Hibernate
> (Object
PROTECTED]
Sent: Montag, 21. August 2006 14:01
To: Tapestry users
Subject: Re: Tapestry with Hibernate vs JSF with Hibernate (Object
binding question)
Sorry for the delay. Well, object equals and hashcodes are fully
implemented. What solved the problem was setting the property
persistent, which I
Sorry for the delay. Well, object equals and hashcodes are fully
implemented. What solved the problem was setting the property
persistent, which I really did no liked :(
When using a volatile property, tapestry is overwriting the objects,
by fresh new ones, filled only with forms values (as I sai
Just to clarify, Tapestry does not overwrite bound objects with new
instances. iow, if a bound value is a Hibernate proxy, that's what
you'll get -- for better or worse ;)
-Ryan
On Aug 19, 2006, at 7:20 AM, Vinicius Carvalho wrote:
Hello there! As I said on previous emails, I'm migrating a
Also, not understanding the problem myself, you might want to check
that the entites have a useful implementation of equals/hashcode. This
sort of thing has bit me more times than I care to remember.. If u
test the objects with an equals/hashcode impl based solely on the
nullable primary key of th
I don't fully understand, but it sounds a bit like you have a property
on your page which should be marked as persistent but isn't.
Could you post some code (java, page, html)?
Cheers,
Detlef
-Original Message-
From: Vinicius Carvalho [mailto:[EMAIL PROTECTED]
Sent: Samstag, 19. August
