Spring Controller annotated with @JsonView and hibernate4

[bademux]

Hello,
It isn't a bug, bug nasty behavior.
I configure my MappingJackson2HttpMessageConverter for using ObjectMapper and Hibernate4Module with SessionFactory

Spring along @JsonView-aware Controller has been used
see for more info: "Jackson’s @JsonView is supported directly on @ResponseBody"

I supposed that all Lazy fields will be initiated and serialized, but got "could not initialize proxy - no Session" on

@ManyToOne(fetch = FetchType.LAZY, optional = false) 
private Test test;

exception goes from
com.fasterxml.jackson.datatype.hibernate4.HibernateProxySerializer#findProxied

return init.getImplementation(); 

Is it expected?

[cowtowncoder]

The first question usually is whether you can reproduce the behavior without spring, just using Jackson and Hibernate module. My guess is that the problem is that Spring controller is trying to serialize things after Hibernate session is closed; if so, this is not something Jackson has any control over.

[bademux]

exactly, but Hibernate4 Jackson module trying to handle this (at least for Collections - check PersistentCollectionSerializer).
Let me ask it in other way:
Why only collection handled in such way? (I see here inconsistency with single reference, o at least undocumented behavioud)
Why hibernate session is opened per object property not per object itself?
Thanks.

[cowtowncoder]

Jackson module does not open sessions as far as I recall. It assumes a session exists, during processing.

Having said that, I do not use Hibernate nor Spring, so someone else may have to help here.
I only help to maintain this module.

[bademux]

Session is opened by hibernate4module, added here: e4b3654 , see for more info:

PersistentCollectionSerializer#openTemporarySessionForLoading()

Hibernate module opens session for read for each collection, but ignoring simple refs.

Please, consider to mark it as a bug if you find inconsistency in the behavior.

cast @eoger :)

upd.
I think, it happens because HibernateSerializerModifier#modifySerializer() is commented out.
But not sure - investigation is needed.

btw, it is really bad approach to open session per property.It is responsibility of another abstraction layer, imho

[cowtowncoder]

I stand corrected. Thank you for pointing this out @bademux.

And that does seem wrong to me as well, since it really ought not to be data-binding layer's responsibility.