A major problem with ORM frameworks trying to pass objects out to the display layer is that the persistable objects often carry some extra freight related to the persistency mechanism - specifically,
JDBC connection objects. This information generally gets ripped loose by the time the display layer gets it, so indirect refences like <c
ut value="${object1.object2.property1}"/> end up failing or showing as null objects.
To function properly, you have to ensure that all the dependent items are force-fetched. That way, they can be located without reference to the persistency subsystem. Since lazy fetching is the norm, you may have to "nudge" the object structure to get everything resolved in the pre-display code while the persistency infrastructure is still active.
JDO can be a real pain in that regard. Hibernate often handles things more gracefully, but even it needs some manual help at times.
Just in case it wasn't clear, the answer is "yes. IF...".
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.