Extends the
MatchingTask class provided in the default ant distribution to provide a
directory scanning EJB jarfile generator.
The task works by taking the deployment descriptors one at a time and
parsing them to locate the names of the classes which should be placed in
the jar. The classnames are translated to java.io.Files by replacing
periods with File.separatorChar and resolving the generated filename as a
relative path under the srcDir attribute. All necessary files are then
assembled into a jarfile. One jarfile is constructed for each deployment
descriptor found.
createWebsphere() Adds a deployment tool for Websphere 4.0 server.
public void
execute() Invoked by Ant after the task is prepared, when it is ready to execute
this task.
This will configure all of the nested deployment tools to allow them to
process the jar.
setBasejarname(String inValue) Set the base name of the EJB JAR that is to be created if it is not
to be determined from the name of the deployment descriptor files.
public void
setBasenameterminator(String inValue) The string which terminates the bean name.
The convention used by this task is
that bean descriptors are named as the BeanName with some suffix.
public void
setClasspath(Path classpath) Set the classpath to use when resolving classes for inclusion in the jar.
public void
setCmpversion(CMPVersion version) Sets the CMP version.
public void
setDependency(String analyzer) Set the analyzer to use when adding in dependencies to the JAR.
setFlatdestdir(boolean inValue) Controls whether the
destination JARs are written out in the destination directory with
the same hierarchical structure from which the deployment descriptors
have been read.
Add a deployment tool to the list of deployment tools that will be
processed
Parameters: deploymentTool - a deployment tool instance to which descriptorswill be passed for processing.
Create a DTD location record. This stores the location of a DTD. The
DTD is identified by its public Id. The location may either be a file
location or a resource location.
the DTD location object to be configured by Ant
Invoked by Ant after the task is prepared, when it is ready to execute
this task.
This will configure all of the nested deployment tools to allow them to
process the jar. If no deployment tools have been configured a generic
tool is created to handle the jar.
A parser is configured and then each descriptor found is passed to all
the deployment tool elements for processing.
exception: BuildException - thrown whenever a problem isencountered that cannot be recovered from, to signal to antthat a major problem occurred within this task.
Set the base name of the EJB JAR that is to be created if it is not
to be determined from the name of the deployment descriptor files.
Parameters: inValue - the basename that will be used when writing the jarfile containing the EJB
setBasenameterminator
public void setBasenameterminator(String inValue)(Code)
The string which terminates the bean name.
The convention used by this task is
that bean descriptors are named as the BeanName with some suffix. The
baseNameTerminator string separates the bean name and the suffix and
is used to determine the bean name.
Parameters: inValue - a string which marks the end of the basename.
Set the classpath to use when resolving classes for inclusion in the jar.
Parameters: classpath - the classpath to use.
setCmpversion
public void setCmpversion(CMPVersion version)(Code)
Sets the CMP version.
Parameters: version - CMP version.Must be either 1.0 or 2.0. Default is 1.0. Initially, only the JBoss implementation does something specific for CMP 2.0.
Set the descriptor directory. The descriptor directory contains the
EJB deployment descriptors. These are XML files that declare the
properties of a bean in a particular deployment scenario. Such
properties include, for example, the transactional nature of the bean
and the security access control to the bean's methods.
Parameters: inDir - the directory containing the deployment descriptors.
Set the destination directory. The EJB jar files will be written into
this directory. The jar files that exist in this directory are also
used when determining if the contents of the jar file have changed.
Note that this parameter is only used if no deployment tools are
specified. Typically each deployment tool will specify its own
destination directory.
Parameters: inDir - the destination directory in which to generate jars
Controls whether the
destination JARs are written out in the destination directory with
the same hierarchical structure from which the deployment descriptors
have been read. If this is set to true the generated EJB jars are
written into the root of the destination directory, otherwise they
are written out in the same relative position as the deployment
descriptors in the descriptor directory.
Parameters: inValue - the new value of the flatdestdir flag.
setGenericjarsuffix
public void setGenericjarsuffix(String inString)(Code)
Set the suffix for the generated jar file. When generic jars are
generated, they have a suffix which is appended to the the bean name
to create the name of the jar file. Note that this suffix includes
the extension fo te jar file and should therefore end with an
appropriate extension such as .jar or .ear
Parameters: inString - the string to use as the suffix.
Set the Manifest file to use when jarring. As of EJB 1.1, manifest
files are no longer used to configure the EJB. However, they still
have a vital importance if the EJB is intended to be packaged in an
EAR file. By adding "Class-Path" settings to a Manifest file, the EJB
can look for classes inside the EAR file itself, allowing for easier
deployment. This is outlined in the J2EE specification, and all J2EE
components are meant to support it.
Parameters: manifest - the manifest to be used in the EJB jar
setNaming
public void setNaming(NamingScheme namingScheme)(Code)
Set the naming scheme used to determine the name of the generated jars
from the deployment descriptor
Parameters: namingScheme - the naming scheme to be used
Sets the source directory, which is the directory that
contains the classes that will be added to the EJB jar. Typically
this will include the home and remote interfaces and the bean class.
Parameters: inDir - the source directory.
Fields inherited from org.apache.tools.ant.taskdefs.MatchingTask