|LazyInitializationException with JAXB [message #760920]
||Mon, 05 December 2011 15:32
| Troy Doty
Registered: December 2011
I did not see a MOXy specific subforum, so forgive me if this is not in the correct place...|
We had been using the reference implementation of JAXB, but it did not provide support for a null policy (at least that I was able to find). MOXy does provide such a solution. However, I was unable to find a similar solution for this problem (when using MOXy): (missing protocol since I can't post links yet) blogs.oracle.com/searls/entry/jaxb_custom_accessor_for_marshalling
We are using Hibernate for our JPA provider (at least for now) and this solution was already in place to handle our lazy init exceptions. Using MOXy with Hibernate, is there a similar workaround for this issue? Basically we don't want lazy init exceptions for JAXB mapped properties/fields that were not fetched.
Any ideas are welcome.
Powered by FUDForum
. Page generated in 0.02400 seconds