• 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
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

accommodating multiple versions of jars

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have 2 web application and they both use different versions of Spring. Unfortunately we don't have all the source for one of the web app. One web app uses Spring 2.0 and we use Spring 3.0 for own own web application. Currently we are keeping Spring jars in each of these web apps under WEB-INF/lib and all things work. We don't want our portlet web apps including Spring jars in each of the web app as it gets bulky. We want to keep all the jars (3.0) in shared lib and let other web app (commercial) use 2.0 jars from its WEB-INF/lib. However, when I used put them in ${catalina.home}/shared/lib/*.jar they are getting picked up by tomcat for commercial web app and the application won't start. How I go about solving this issue?

Any suggestions or pointers are most welcome. FYI, I'm using tomcat 6.0.26 version.

Thanks,
mtalluri
 
Sheriff
Posts: 67650
173
Mac Mac OS X IntelliJ IDE jQuery TypeScript Java iOS
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

murali talluri wrote:We want to keep all the jars (3.0) in shared lib ...


You shouldn't. Putting the required jars in each web app's WEB-INF/lib is the correct approach.

Disk space is cheap; so what if it's "bulky"?
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic