|
AIEEEEEEEEEEEE! You're bringing back repressed memories of Xerces incompatibilities. Many a sleepless night was due to trying to get two packages working when they required incompatible versions of Xerces.
Given the fact that gigabytes are no longer uncommon for applications, I definitely favor including all my required libraries in the deployment unit (EAR or WAR). Then the only issue is making sure that the end user doesn't deploy them on an app server with a different version of your libraries. At that point you're talking about class loading sequences and custom classloaders and my eyes start to glaze over...
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.