• 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
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Disadvantages of using the standard extensions directory

 
Ranch Hand
Posts: 331
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The convenience of putting your jars in lib/ext is great. But does that mean we should?
From jdom.org:


You need to ensure that the xerces.jar file supplied with the JDOM download is in your classpath before any other XML classes, such as those that come with JAXP or Crimson


So in this case, it seems that you can't just place the jars in lib/ext, instead you must rely on your CLASSPATH so that you can enforce the order by which the jars are loaded.
I'd like to know if anyone has any thoughts on using lib/ext. Should we freely use it for any jars (except, of course, xerces.jar if using jdom)? Or should it just be reserved for "core" extensions from Sun, such as activation.jar, mail.jar, etc? Is there a convention/standard for when to use it?
 
reply
    Bookmark Topic Watch Topic
  • New Topic