ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Holger Engels <heng...@mercatis.de>
Subject [PATCH] EjbJar, GenericDeploymentTool, WebsphereDeploymentTool
Date Tue, 20 Nov 2001 10:33:37 GMT


o the GenericDeploymentTool uses the utility class Dependencies, that is
  also used in the classfileset. As a new Feature, it supports the 
  inclusion of manifest files by naming convention (basename-manifest.mf)

o Enhanced / Fixed the WebsphereDeploymentTool, that was originally posted 
  from Maneesh Sahu. Now it works at least on Linux and Win2K and uses 
  the Java-task to call was4's ejbdeploy. Usage:

  <property name="websphere.home" name="/opt/WebSphere/AppServer"/>

  <path id="was4.ejbdeploy.classpath">
    <pathelement 
location="${websphere.home}/deploytool/itp/plugins/org.eclipse.core.boot/boot.jar"/>
    <pathelement 
location="${websphere.home}/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime/batch.jar"/>
    <pathelement location="${home.was4}/lib/xerces.jar"/>
    <pathelement location="${home.was4}/lib/ivjejb35.jar"/>
    <pathelement location="${home.was4}/lib/j2ee.jar"/>
    <pathelement location="${home.was4}/lib/vaprt.jar"/>
  </path>

    <ejbjar srcdir="${build.class}"
	    descriptordir="${build.etc}/ejb">
      <include name="*-ejb-jar.xml"/>
      <websphere dbvendor="${dbvendor}"
                 oldCMP="false"
		 quiet="false"
		 keepgeneric="true"
		 tempdir="/tmp"
                 destdir="${dist.server}">
        <wasclasspath>
          <path refid="was4.ejbdeploy.classpath"/>
        </wasclasspath>
        <classpath>
          <path refid="was4.classpath"/>
        </classpath>
      </websphere>
    </ejbjar>

The ugly classpath is required, to get the deployment tool running. We 
could hardcode it in the WebsphereDeploymentTool instead ... suggestions?

o EjbJar enlists the WebsphereDeploymentTool


Holger Engels

Mime
View raw message