• 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Bear Bibeault
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Jj Roberts
  • Tim Holloway
  • Piet Souris
Bartenders:
  • Himai Minh
  • Carey Brown
  • salvin francis

shared library packaging

 
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi experts,

I have some shared jars (some data models, etc) that will be used by several application modules. I am facing some choices:

1. package these shared jars inside the application moduels.
2. put in the shared library of Websphere application server.

Which way is better? What's the pros and cons?

If in future I need to support weblogic or other application servers, any impact?

I am considering version conflict issue if put in the shared library, how do you think of it?

Thanks,
JX
 
author & internet detective
Posts: 40283
819
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Howie,
I would go with #1. You don't want unneeded dependencies between applications. This makes it harder for one app to upgrade. It also makes the application less self contained and more reliant on the environment.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic