Details
Description
I've got a system where I could use everything about NanoContainer Deployer EXCEPT that I have my composition script in a different location inside the virtual file object. If we considered NanoContainer.getDeploymentScript() more of a template method and made it protected, it would save me a lot of time in the long run and I'd still get to test out/improve the main Deployer code.
If there was an objection to just making it protected, I wouldn't mind creating an abstract base class for NanoContainerDeployer that took care of the common tasks and made getDeploymentScript() a "pure virtual" function that way.
ie:
abstract public class AbstractNanoContainerDeployer() {
.....
abstract protected FileObject getDeploymentScript(FileObject applicationFolder);
}
Activity
Field | Original Value | New Value |
---|---|---|
Project | NanoContainer Sandbox [ 11010 ] | NanoContainer [ 10121 ] |
Key |
|
|
Component/s | deployer [ 11788 ] | |
Component/s | deployer [ 11641 ] |
Resolution | Fixed [ 1 ] | |
Fix Version/s | 1.0-RC2 [ 11851 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Completed.