Hello,

I am using the following mapping:



I am using DOM4J entity mode. When I load "up_CardInformation" entity, Hibernate (3.2.5) also loads "up_cardUsage" collection regardles of default lazy mode. I tried to set lazy attribute = "true" for "up_cardUsage" list, but it does not help. From the other hand, lazy collection loading works fine, if I switch entity mode to MAP.

I found out, that org.hibernate.type.CollectionType.getCollection(Serializable, SessionImplementor, Object) method ignores lazy collection loading mode, because of initializeImmediately(EntityMode) method:


1. As I understand, there is no any way to use lazy loading for DOM4J entity mode. Am I correct?

2. Using DOM4J entity mode, I found some other bugs/problems like https://forum.hibernate.org/viewtopic.php?f=1&t=957391, impossibility of using null values. Does MAP entity mode free of such critical bugs?

I agree, it would be useful to be able to use the "lazy" attribute to specify what is loaded into a dom4j object graph. Really there is not a good way to only serialize only part of a dom4j xml object graph. In my case, I have a large graph, with a large amount of data, so loading the whole object graph provides way too much overhead.

I realize I could accomplish this using separate xml "entities" for the same table, but this is alot of extra mapping, and really isn't very maintainable.

The other alternative is to just fetch the actual pojo object graph, then use one of the many object to xml marshalling frameworks. However, this seems like alot of extra overhead, and requires some unique conventions to handle hibernate proxy classes (JAXB custom Accessors for example).