I understand that GlassFish supports directory deployment (aka exploded
deployment), at least as far as JEE Modules (ejb .jar, .war, .rar) go.
And, the JEE 5 spec provides that an .ear file can have a directory, by default
named "lib", at the root of the enterprise archive that contains "Bundled
Libraries" (.jar files of classes and resources that need to be available on the
class path of all JEE modules in the application).
I would like to suggest an enhancement to support deploying Bundled Library jars
as exploded directories, for example the "mylibrary-1.0_jar" shown below:
We have a variety of bundled libraries that are simply dependent jar files such
as log4j that we'd never need to deploy exploded (and we wouldn't want to have
to explode them). But, then we also have several other bundled library jar files
that contain code that we authored and that our JEE modules (web apps and
perhaps ejb modules) need to share and depend on.
Our objective is to to be able to hot deploy changes to these shared bundled
library projects in the same way that we can update a class or jsp in the
exploded web app.
I realize this all can be done with manifest class paths, but it would be
valuable not to have to add special logic to our build files to add manifest
class path entries for exploded deployment when that isn't relevant for packaged
Ideally, the directory structure, locations and names of everything would be
exactly the same between packaged and exploded deployment, except that in the
latter case some jar and war files are exploded as directories and have "."
replaced with "_" in their filenames.
Thanks for your consideration of this idea.