Seam-managed PCs let you avoid LIE's while inside the conversation scope.
The *do not* solve this problem for the whole session scope.
Thanks. I converted those beans accordingly. No more LazyInitException.
Back to this error now, though:
11:02:43,668 ERROR [STDERR] org.hibernate.TransactionException: could not register synchronization w ith JTA TransactionManager at org.hibernate.jdbc.JDBCContext.registerSynchronizationIfPossible(JDBCContext.java:174) at org.hibernate.impl.SessionImpl.checkTransactionSynchStatus(SessionImpl.java:1824)
As I make progress in other areas, I eventually just end up with this error again. Is anyone else getting this? I don't even know where to start looking to solve this one.
One thing I discovered is if you override the toString() method and output the relationships, it'll force the container to load the relationship related fields. I'm thinking it accomplishes the same thing as fetchtype.eager but i've had more luck with this. Plus it works dual fold since I use the toString() method in conjunction with facesMessages to display what the object coming back is.