We are integrating Hibernate Search (3.0.0 GA) into an existing Hibernate / Spring Framework / Eclipse RCP configuration. Unfortunately, Hibernate Search's FullTextSessionImpl assumes that it will be passed an org.hibernate.classic.Session. When using Spring for Hibernate transaction management, Spring creates a defensive Proxy that disables the Session.close() method. This Proxy does not implement the EventSource nor classic.Session, while Hibernate Search assumes that it does and has a ClassCastException in the FullTextSessionImpl constructor.

Hibernate Search's FullTextSessionImpl does this which is wrong for the Spring Hibernate Session Proxy:

public FullTextSessionImpl(org.hibernate.Session session) {
this.session = (Session) session; // classic.Session!
this.eventSource = (EventSource) session;
this.sessionImplementor = (SessionImplementor) session;
}

It should be possible to rewrite FullTextSession and FullTextSessionImpl so that they do not use the org.hibernate.classic.Session but instead use the standard Hibernate Session, and thus avoid the unsafe casting.

The workaround for this is to use HibernateTemplate.setExposeNativeSession( true ) before executing the HibernateCallback (causing the SessionImpl to be passed directly, without a Proxy). This exposes the Session to potential close() and is *not* a good idea.


I've filed this as a bug here:
http://opensource.atlassian.com/project ... SEARCH-148

And I'm posting to these forums so that people can easily google search this on site:hibernate.org

If anyone has experience integrating Hibernate Search with Spring transaction management, please chime in. Cheers.

No Hibernate Search has to have access to EventSource (actually SessionImplementor) because it plays with the transaction state.
so really Spring should implements all the necessary interfaces in their wrapper proxy.

Thanks emmanuel for the prompt reply! And thank you very much for all the hard work you've put into Hibernate Search and these forums!

If the FullTextSessionImpl requires a org.hibernate.classic.Session and EventSource, shouldn't it take those as parameters to the constructor (and Search.createFullTextSession should too)? What's there right now with the unsafe downcasting explodes at runtime instead of being enforced at compile time...

I've filed a bug with the Spring framework to have their proxy implement the additional interfaces needed by Hibernate Search:
http://jira.springframework.org/browse/SPR-4341

According to the JIRA report this problem has been addressed in spring 2.5.2