Details
-
Type:
Wish
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0-RC2
-
Fix Version/s: None
-
Component/s: deployer
-
Labels:None
-
Number of attachments :
Description
Before I was a commiter, I had to fork some of my code from Deployer because I had a different file format than Deployer Mandated. So what I'd like to see is a 'ArchiveFormat' interface that specifies where things like:
Peer Jars Are
Composition Script Name and Location
Where container Classes are.
So, if a WAR file was deployed via deployer. (Not that we would, but we all know that format well)
ArchiveFormat format = new WarFileFormat();
assertEquals("/WEB-INF/composition.groovy" format.getCompositionScript()) //Possibly Mutiple Scripts Too.
assertEquals("/WEB-INF/classes", format.getClassLocation())
//PseudoCode: assertTrue(format.getPeerJars().equals(archive.AllJarsIn("WEB-INF/lib"))); These would then be added
//to the VFS classloader path I've done something similar to this and it works great.
Of course, the file format could be specified in the NanoContainer deployer constructor.
Activity

Field | Original Value | New Value |
---|---|---|
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
This behavior is currently inside Pico 3.0-SNAPSHOT modules.