• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
  • Paul Clapham
Sheriffs:
  • paul wheaton
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Piet Souris
Bartenders:
  • Mike London

Tomcat on Solaris, common/lib problem

 
Ranch Hand
Posts: 68
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have added several jar files to common/lib and they seem to load fine, but when I add a third the classes that are in it are not being found, and the result is NoClassDefFound errors.
When I unpack the jar into the classes directory instead of putting the jar i the common/lib it seems to work fine.
Anyone seen this before? The jar not being found is rather large compared to the rest, about 8.5 megs.
OS: Solaris 8
Tomcat: 4.x
J2SE: 1.3.1_03
Thanks Guys and Gals!
-Jason
 
Ranch Hand
Posts: 95
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You can also try dropping these jar files in the WEB-INF/lib directory of your webapp:
http://java.sun.com/j2ee/tutorial/1_3-fcs/doc/WCC3.html
 
Saloon Keeper
Posts: 26550
187
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I don't think that common/lib is intended for application support classes - there's a separate lib directory where I put my database support jars, at least. For app-specific jars, the webapp's WEB-INF/lib directory is what you should be using - otherwise you won't deploy properly should you move to another appserver - not even a Tomcat 3 one.
 
reply
    Bookmark Topic Watch Topic
  • New Topic