Win a copy of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

shared library packaging  RSS feed

 
Howie Jiang
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
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 37180
515
Eclipse IDE Java VI Editor
  • 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.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!