Hi,

I am trying to use FullTextSession object for hibernate search indexing. But Search.getFullTextSession(session) returns org.hibernate.impl.SessionImpl java.lang.ClassCastException. Not sure what is going wrong. Here is a code snippet :

import org.hibernate.*;
import org.hibernate.cfg.Configuration;
import org.hibernate.search.FullTextSession;
import org.hibernate.search.Search;


public class FirstExample {
public static void main(String[] args) {
Session session = null;
Transaction transaction = null;

try{
// This step will read hibernate.cfg.xml and prepare hibernate for use
SessionFactory sessionFactory = new Configuration().configure().buildSessionFactory();
session = sessionFactory.openSession();
Transaction tx = session.beginTransaction();
FullTextSession fts = Search.getFullTextSession(session);

}catch(Exception e){
System.out.println(e.getMessage()+ " " + e);
}finally{
session.flush();
session.close();

}

}
}


As per compatibility matrix, here are the jar version I am using

hibernate3.jar
hibernate-commons-annotations-3.1.0.GA.jar
hibernate-entitymanager-3.4.0.GA.jar
hibernate-search-3.1.1.GA.jar
hibernate-annotations-3.4.0.GA.jar
hibernate-core-3.3.1.GA.jar
lucene-core-2.4.1.jar

I have tried to debug in the source code but doesn't make much sense for class cast exception.

Thanks in advance.

Cheers
Manoj

What's the full stack trace?
Regarding your dependencies -hibernate3.jar is just Hibernate Core. I don't think you need it.

--Hardy

Hi Hardy,

The only exception that I get in stacktrace is ClassCastException: Cannot cast org.hibernate.impl.SessionImpl (id=18) to org.hibernate.event.EventSource. There is nothing more than this in the stacktrace. when I debugged the code right inside the source file of FullTextSessionImpl, I found that the error occurs when it there is type casting of a session object with EventSource.

this.transactionContext = new EventSourceTransactionContext( ( EventSource ) session );

I am just wondering if the there is any problem with the session object that I am trying to create.

Manoj

Somewhere there should be more context to this error. Have you checked all log files? Is your application / IDE somehow swallowing the exception somewhere?
My guess would be that you have a wrong setup somehow or class conflicts. Is your application a standalone Hibernate app or are you developing a web or J2EE application? Are you using any additional framework?

--Hardy

I am using eclipse for development and don't see any problem with logs. I can print stacktrace for other errors I throw explicitly.

But I agree with you, that the project configuration could be an issue or that there might be a class conflict. I am running this as a standalone application and dont have any framework apart from hibernate.This is just like a POC which I am doing before I actually move that to my web application.

However, I have observed that my project doesnt compile without hibernate3.jar and hibernate-core-3.3.1.GA.jar both in classpath. When I remove hibernate3.jar from project, it has issue creating SessionFactory object and throws null pointer exception for session object. If I remove hibernate-core-3.3.1.GA.jar it has issue with the Eventsource object. Does that problem makes sense with the jars I am using ?

You should remove hibernate3.jar from the classpath, and fix your problems to have it compile properly: you can't have both on classpath as they contain the same classes in different versions, so they're creating a huge mess.

Thanks a lot for all your help. I did resolve this. There was compatibility issue with the hibernate and hibernate search jars that I was using.

But I still fail to understand how there could be issues be Session object in 2 different jars.

--Manoj

because you won't control which one you're loading :)
this gets you very randomic and non-predictible issues; this applies to all java applications, with the exceptions of different applications in an application server, but still you have to be careful: be aware of what you do, understand and setup classloader isolation.
If you want to keep it simple, never put duplicate classes in your classpath.

To make sure you don't have more duplicates, use a tool ass JBoss Tattletale http://jboss.org/tattletale, it's a command line tool which inspects your application and produces a great report with warnings about this.
For in depth detaials, see also webinar #8 at : http://www.jboss.org/webinars

BTW if you used Maven to manage your dependencies you would avoid all the mess.

I also recommend to get an IDE independent build (ant, maven, gradle or whatever you want) with clearly specified dependencies.

--Hardy