Hello. I'm trying to use H.Tools
I'm using annotated classes for the model. I work with Myeclipse5.1.1.
I've installed the last H.Tools plugin. Under my "Hibernate Configurations" now I've all my classes and the "Database" tables shows correctly.
The problem is that whenI try to run a new hql with the "HQL Editor" I don't see anything. I click on run and nothing goes on.
On my Hibernate Console Configuration I've set
Type: Annotations
Configuration file: \MyProject\src\hibernate.cfg.xml
and in Classpath I've added the mysql jdbc jar (I think it doesn't need that)
Someone can help me
regards :)

Solved.. I have created a new 'Hibernate Console Configuration' and now this works.. I don't know why but it works.. and this's the important thing! :D

Actually, I have the same problem.

I use a Oracle10g Database and the 3.2 beta 8 version of Hibernate.

I have a Console Configuration with the classpath of the oracle driver and also my sources:
csr/lib/ojdbc14.jar
csr/src
csr/class

When I now use ReverseEngineering everything looks fine. And if I enter a correct HQL query like: "from Test" or "select t.id from Test t" I just get a empty output.

Can somebody help me with that problem? I also tried to make a new configuration but that didn't helped. Have you perhaps done something other than before???

edit: When I copy the generated SQL query and paste it into a direct sql-editor for my database, I get the right information...

before trying to solve issues, please use beta9

Okay, I doesn't know what the hell happened but when I started eclipse today at first the Configuration didn't worked. So I made a new run from the reverse engineering and suddenly even HQL works! I've made so many reverse engineerings before and until know I haven't made a update...it is really very strange what happened here!

And even more strange is, that I'm not the only one with this experience...

What do you mean by "Configuration didn't worked" ...?

Sounds like you actually this time "started" the sessionfactory in the configuration so the query would actually work.

Maybe my error handling for showing a "Session Factory not started" does not catch a specific case that you are hitting.

I had started the SessionFactory every time when it didn't worked. I'm sure I tried everything which was possible for me. The good thing is that the error never happened again.