Hi,

I can't get the reverse engineering to work. I'm using the Eclipse plugin. If I enter: org.hibernate.cfg.reveng.DelegatingReverseEngineeringStrategy
into the 'reveng.strategy' field or nothing at all it works. BUT when I enter my custom strategy class I get the following error:


As if my class didn't have the (explicitly required) contructor wich calls the super with a delegate... How is this meant to work?

I guess your strategy class is not in Console configuration class path?

And what does that mean? I tried packing the class into a jar and put it right next to the other hibernate jars. Plus, adding it to the build path, so it appears under "Referenced Libraries" in Eclipse...

That is exactly what is was. But when you look at my previous post you'll see that this is not something that can be considered common knowledge. Since I created this configuration once when starting on my hibernate project, I quickly forgot about it. Because it always gets chosen automatically when reverse engineering. Plus, it didn't matter if I worked in different Eclipse projects.

How is someone supposed to know that this (one time only seen) configuration:

• uses the class path of the very first project you set it to (so the source file needs to be copied to there)
  
• it is a class path problem in the first place, since the error message clearly suggests that a required constructor was missing! Which is total BS since it is impossible to extend the DelegatingReverseEngineeringStrategy without having a proper constructor present!

So thanks again for directing me to the right path. But again, this was way more complicated that it needed to be. If only the sites explaining the custom reverse engineering strategy would include these facts.

Because again, I don't think it is that uncommon to have more than one Eclipse project for which you didn't create a sepparate Hibernate Configuration. (Which would be always exactly the same anyway, except for the project's class path of course)

The error message says constrictor could not be found since the class could not be found.

And I'm sorry you missed that console configurations have a class path associated with them but if you think about it how should we choose the class path if not by having it on the console configuration launch? Should we just choose to use a new class path based on your current selection instead ?that would lead to even more confusion. Don't you think ?