Simplify Your Application Delivery with One-JAR

By P. Simon Tuffs
2005-04-22


Overview of One-JAR
Before I describe the details of One-JAR, let me first discuss the goals I had in building it. I decided that a One-JAR archive should:

• Be executable using the java -jar mechanism.

• Be able to contain all of the files needed by an application -- that is, both classes and resources in their original (unexpanded) form.

• Have a simple internal structure that could be assembled using only a jar tool.

• Be invisible to the original application -- that is, the original application should be able to be packaged inside a One-JAR archive without modification.

Tutorial Pages:
» Power Programming with Custom Classloaders
» Overview of One-JAR
» Problems and solutions
» Enter the JarClassLoader
» Loading Resources
» Bootstrapping the JarClassLoader
» In Conclusion
» Resources


First published by IBM DeveloperWorks

Related Tutorials: » All about JAXP, Part 1 » Make Database Queries Without the Database » Load List Values for Improved Efficiency » 2 Ways To Implement Session Tracking » A Simple Way to Read an XML File in Java » Develop Aspect-Oriented Java Applications with Eclipse and AJDT