J2EE Packaging and Common Code
From the developerWorks archives
Date archived: January 4, 2017 | First published: July 11, 2002
Common code libraries that provide common function to multiple J2EE applications at run time are extremely valuable and provide a number of benefits. But how should these common code libraries be packaged? This article discusses the benefits, challenges and risks of run-time sharing, and of providing J2EE applications with their own local copies of common code binaries.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.