[Lee Harrington]

Previous story:

I had a jdom problem in a previously working application, but when I upgraded to the first hibernate version (which I believe was 3.7.2), it stopped working.

Problem solved by copying the jdom.jar in to my WEB-INF\lib directory of my deployed project.

Supposedly 3.8.1 fixed this, so I upgraded.

Then I undeployed my project and redeployed. Received the same “noclassdef found” error. This time, though, I knew right away to copy the jdom.jar into my deployed app’s WEB-INF\lib directory (instead of taking 2 days of debugging to find that out).

Problem once again fixed.

And while knowing what to do to fix the problem lets me continue on with my work, I’d be very happy to help you guys fix this bug.

Lee

[Riyad Kalla]

Lee,
Going off of the previous report this was an externally referenced class correct? Right click on your project and double check your deployment preferences to make sure its setup to deploy your external libraries… default is to not deploy them I believe.

[Lee Harrington]

@support-rkalla wrote:

Lee,
Going off of the previous report this was an externally referenced class correct? Right click on your project and double check your deployment preferences to make sure its setup to deploy your external libraries… default is to not deploy them I believe.

That did it. Was that the problem this entire time? Why did it work before and then stop? Or was this part of the new fix?

Where should we place “external jars” such that we wouldn’t have to include them with each project?

Lee

[Riyad Kalla]

Lee,
There was a bug in 3.8.0 GA that ignored these resources, it was fixed in 3.8.1.

As far as your second question, that really depends on you. If you need the JAR for your application to function, then it should likely be in your WEB-INF/lib dir… if you are just linking to it for compile-time resolution then just leave it as an external reference… etc. etc.

[Author]

Posts