Thanks for the reply Max, but alas, that is not the case. I only have one hibernate2.jar in my classpath.
I think it's a Spring problem as I can create a Configuration object in my own code and call the setNamingStrategy method on it, yet when I get Spring to configure itself from my XML config file, it encounters the problem.
I've even created a Configuration object in my code, called setNamingStrategy on it, then let Spring do its thing, and the Spring code encounters the problem. So, it doesn't seem to be a class loading problem (as far as I can tell in my (limited) java experience).
I have tried the latest release of Spring too - 1.1.2, to no avail.
For now, I'm going to go back to 2.1.6, having wasted the whole morning trying to find the solution to this. :-(
Any other suggestions most welcome!
Craig
|