I disagree with not advertising this issue. EclipseLink has this feature and it's "often" referred to as one of the main advantages of using EclipseLink. Hey - I actually very seriously considered switching to EclipseLink my self because of this (after 7 year of using Hibernate).
This feature saves developers developing web-apps very much hassle and developers developing the service-layer can now code more naturally without having to call Hibernate.initialize() in their application-services or resort to exotic lazy-init-aspects (as I did). This really keeps the code cleaner.
I disagree with not advertising this issue. EclipseLink has this feature and it's "often" referred to as one of the main advantages of using EclipseLink. Hey - I actually very seriously considered switching to EclipseLink my self because of this (after 7 year of using Hibernate).
This feature saves developers developing web-apps very much hassle and developers developing the service-layer can now code more naturally without having to call Hibernate.initialize() in their application-services or resort to exotic lazy-init-aspects (as I did). This really keeps the code cleaner.
Keep it up, great work!