WebSphere Deployment Tool for ejbjar

[Todd Chambery <tc...@hotmail.com>]

Hey all,

I've gotten a Websphere deploy task written and running (borrowing very
heavily
from the WeblogicDeploymentTool class), with one major hurdle remaining:  I
can't figure out how to
    a) put my own manifest into the generic ejb jar created by the
GenericDeploymentTool, or
    b) overwrite the default manifest added by the GDT.

To solve a), I tried overriding the GDT method writeJar (this is where the
default
manifest is added) but the GDT instance var addedFiles is used by another
GDT method, addFileToJar, and is not accessible to the subclass, so this
comes up as :

java.lang.NullPointerException
        at
org.apache.tools.ant.taskdefs.optional.ejb.GenericDeploymentTool.addFileToJa
r(GenericDeploymentTool.java:245)
        at
org.apache.tools.ant.taskdefs.optional.ejb.WebsphereDeploymentTool.writeJar(
WebsphereDeploymentTool.java:471)

The problem with overwriting as in b), is this:

   [ejbjar] adding file 'META-INF/MANIFEST.MF'
   [ejbjar] WARNING: IOException while adding entry META-INF/MANIFEST.MF to
jarfile from
D:\projects\D2V1\ant_descriptors\data_access_Action\Meta-inf\data_access_Act
ion-MANIFEST.MF java.util.zip.ZipException-duplicate entry:
META-INF/MANIFEST.MF

If I may be so bold, I think there's a flaw in the design of the
GeneralDeploymentTool.  You're only allowed to specify a single absolute
path to the manifest file for _all_ descriptors, when, at least in my
current project, each of the ejbjars has its own manifest containing the
classpath for that jar.

Also, what is involved in submitting my WebsphereDeploymentTool class for
inclusion in the ant distro?  I can't really use it on my work projects if
it's not "supported" by the Ant people (which is about the only place anyone
would use WAS).


thanks,

Todd




--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>