Re: javassist/hibernate enhanced class problem

Mabet use an interface for the objects? Then the implementation class can change all it wants to. On Thu, Oct 29, 2015 at 11:40 PM, Paul Stanton wrote: > further, it is not the 'save' that javassistifies the object, it is > 'session.load' ! so if you do a session.load(id)

Re: javassist/hibernate enhanced class problem

On Thu, 29 Oct 2015 20:40:29 -0200, Paul Stanton wrote: further, it is not the 'save' that javassistifies the object, it is 'session.load' ! so if you do a session.load(id) and a criteria.list() which returns the same entity, the list will contain a javassisted

Re: javassist/hibernate enhanced class problem

On Thu, 29 Oct 2015 07:23:07 -0200, Paul Stanton wrote: I have found an issue I believe with tapestery (grid component in this case) where it cannot inspect details of hibernate 'enhanced' objects. This happens when I save an object to the database and then query it

Re: javassist/hibernate enhanced class problem

Hi Thiago, Using 'merge' instead of 'save' does not resolve the issue. I still have to evict. On 29/10/2015 11:04 PM, Thiago H de Paula Figueiredo wrote: On Thu, 29 Oct 2015 07:23:07 -0200, Paul Stanton wrote: I have found an issue I believe with tapestery (grid

Re: javassist/hibernate enhanced class problem

further, it is not the 'save' that javassistifies the object, it is 'session.load' ! so if you do a session.load(id) and a criteria.list() which returns the same entity, the list will contain a javassisted version of the object, which doesn't play nice with tapestry.grid. using 'get' instead

Re: javassist/hibernate enhanced class problem

Yes, it is necessary to 'evict' after 'save' to avoid this problem. I'm not sure that this is ideal since it increases db io and code but it works. On 29/10/2015 8:23 PM, Paul Stanton wrote: I have found an issue I believe with tapestery (grid component in this case) where it cannot inspect