Developing J2EE utility JARs in WebSphere Studio Application Developer
From the developerWorks archives
Date archived: January 3, 2017 | First published: December 12, 2001
When using third-party or utility classes in J2EE applications, you have a variety of choices about where to store them. This article explores the advantages and disadvantages of each location, and describes the best way to make them available to other modules in the application. The article describes a development scenario using WebSphere Studio Application Developer, and includes a simple plug-in that can periodically zip up a Java project into a JAR file within another project.
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.