As written in the forum post this might be related to the scope of the
EntityManager which indeed could have changed when moving away from
seam. I would need more insight into your code to be able to give you a
better answer or hint.
Mit freundlichen Grüßen,
------------------------------------------------------------------------
*Christian Beikov*
Am 08.05.2013 23:40, schrieb Ben Maisano:
Thanks Christian. Well site says seam 3 no longer supported (recent change?)
so I thought this is my best option besides hibernate forum. Note this was all
working, same mappings, on seam 2. hibernate.initialize and fetch.eager do
solve problem. The issue is we have a large dependent entity model and to
change everything to fetch.eager is not an option for us.
-----Original Message-----
From: Christian Beikov [mailto:[email protected]]
Sent: Wednesday, May 08, 2013 5:34 PM
To: [email protected]
Subject: Re: LazyInit exception with hibernate integration
Answered you in forum, but I don't quite understand what this has to do with
deltaspike...
Mit freundlichen Grüßen,
------------------------------------------------------------------------
*Christian Beikov*
Am 08.05.2013 23:13, schrieb Ben Maisano:
Hi DeltaSpike users,
I am thinking of using deltaspike once it comes out of beta,
however right now we are using seam 3. I thought this best list to ask about
this question besides hibernate forums. If anyone can help with ideas for what
to look for related to the details in this post please let me know, thank you.
https://forum.hibernate.org/viewtopic.php?f=1&t=1026107
Benjamin Maisano
