I'm sad to say, it's as simple as that jar not being available to your applications when they are deployed.
Identify which application is throwing that exception, and then find out where the jar file containing that class comes from. Make sure it's either packaged with the app, or placed on the classpath of the server, although depending on how classloaders are configured, that might not be the silver bullet.
In all likelihood, the developers linked to the jar file externally during development, so it wasn't part of the deployed application, and now you're having a ClassNotFoundException on the server.
Hope that helps!
-Cameron McKenzie
_________________ Cameron McKenzie - Author of "Hibernate Made Easy" and "What is WebSphere?" http://www.TheBookOnHibernate.com Check out my 'easy to follow' Hibernate & JPA Tutorials
|