| I think you can definitely define a generic "deployer" interface,
|but the problem is how to represent the thing to be deployed. I think the
|only generic way to do it is as an InputStream or ClassLoader, though you
|could always start with a JarFile... In any case, it's probably safe to
that would make it "file" dependent I much prefer your first option when we
go to "clustering" and the deployer isn't physically where the repository
is.
Take the low level approach.
|define the types or archives that an EAR may contain, but you could
|definitely do as you suggest and use multiple instances of the same
|"deployer" interface for the different archive types:
|
|earDeployer.registerDeployer(".war", new WarDeployer());
|earDeployer.registerDeployer(".jar", new EjbDeployer());
|...
pfffff....
|
|earDeployer.deploy(ear)
| calls getDeployer(".war").deploy(war) for each WAR
| getDeployer(".jar").deploy(jar) for each JAR
| ...
|
|Aaron
sure, except for "registration"
marc
|
|
