Thanks, but I already tried that and it failed too.
I think I will agree with Mark, it has something to do with improper classpath. Perhaps it could be that I am depending on Eclipse inbuilt compilation option and so unable to give correct classpath for the Hibernate Tool. And hence, it might be complaining about it.
I will write my own build script and set the classpath and see how it goes.
Thanks once again. [ December 03, 2007: Message edited by: Bindesh Vijayan ]
This may not be your problem but JPA/Hibernate threw a similar run-time error for me, and I was able to correct it. When I moved a shared package (the database layer) to its own project, it compiled correctly but JPA/Hibernate threw this same type of error at run-time. When I moved the package source back to where it was previously (within the main project) it worked again. I think that the persistence.xml local to the main project didn't know about the classes that were in the other project (the one to which I moved the package that contained the source mapping the class to the database for the class referenced in the exception). I'm experimenting with putting all code that accesses Hibernate into the database package, so that the main project need not reference Hibernate at all, and then making another attempt at moving the package to its own project. If this isn't helpful to you, perhaps it at least gets my own experience out there into the ether in case it might help someone.