Deploy Module

For the Sun Refererence Implementation Application Server the following Writers: -

For the Web Logic Application Server the following Writers: -

J2EE Deploy Module

The J2EE Deploy Module is responsible for the following packaging and deploying J2EE applications.

The Packaging Module contains the following classes:-

  • com.javelin.generator.packaging.EJBJarPackager
  • com.javelin.generator.packaging.ClientJarPackager
  • com.javelin.generator.packaging.WebDeploymentDescriptorWriter
  • com.javelin.generator.packaging.WarPackager
  • com.javelin.generator.packaging.EarPackager

The Packaging Module also contains the following classes that are specific to deploying to Suns RI.

  • com.javelin.generator.packaging.ri.RIEarPackager
  • com.javelin.generator.packaging.ri.RIUndeployer
  • com.javelin.generator.packaging.ri.RIDeployer

In order to deploy to the RI module you need to include the following writer:

$GENERATOR.AggregateWriter rideploy

The Deploy Module also contains the following classes that are specific to deploying to WebLogic.

  • com.javelin.generator.packaging.weblogic.WLEarPackager
  • com.javelin.generator.packaging.weblogic.WLUndeployer
  • com.javelin.generator.packaging.weblogic.WLDeployer

In order to deploy to the Web Logic module you need to include the following writer:

$GENERATOR.AggregateWriter weblogicdeploy

Class Hierarchy

The top-level J2EE Deploy Writer class hierarchy is illustrated below: -

 

The top level Sun Deploy Writer class hierarcy is illustrated below: -

The top level Web Logic Deploy Writer class hierarcy is illustrated below: -

Deploy Properties

The EJB pathName is where all the Java and web files are deployed to and packaged. The EJB path name defaults to the web path path name if that is not set. To set the EJB Path Name use the following syntax: -

ejb.pathName=<path>

The Deployers and Undeployers get a list of servers to deploy and undeploy to. For example: -

ejb.serverName.0=appserver1
ejb.serverName.1=appserver2

By default for remote objects the jndiContextName is not set, and the Home class name is used as the ejb reference in the xml descriptors. To override this default and prefix a name to the ejb jndi names use the following syntax:

[<className>.]ejb.jndiContextName

For example: -

Account.ejb.jndiContextName="northwind1.";

The EJBAccountHome and EJBAccountSessionHome will now be bound to the jndi name: -

northwind1.EJBAccountHome

EJB Jar Packager (com.javelin.generator.packaging.EJBJarPackager)

This is responsible for building the ejb.jar file.

A list of files to deploy in the EJB jar can be given. A set of defaults is provided.

This allows specification of the path and the sub package within that path, using the following syntax: -

ejb.deployClasses.<index>=<path>,<package path>

For example: -

ejb.deployClasses.0=$ROOT/web/WEB-INF/classes,/com/javelin
ejb.deployClasses.1=C:/javelin/jbeans/src,com/javelin/beans

Client Jar Packager (com.javelin.generator.packaging.ClientJarPackager)

This is responsible for building the client.jar file.

A number of library jars can be packaged in the client jar. This is done using the following syntax.

client.libraryJars=[file[;file]

A list of files to deploy in the Client jar can be given.

This allows specification of the path and the sub package within that path, using the following syntax: -

client.deployClasses.<index>=<path>,<package path>

For example: -

client.deployClasses.0=$ROOT/web/WEB-INF/classes,/com/javelin
client.deployClasses.1=C:/javelin/jbeans/src,com/javelin/beans

Web Deployment Descriptor Writer (com.javelin.generator.packaging.DeploymentDescriptorWriter)

The Web Deployment Descriptor Writer is responsible for writing the war descriptor file.

The Web Deployment Descriptor Writer will describe any files it finds under the web.pathName, with the extensions listed in the web.servletExtensions property.

This currently defaulted in the default bdl file to: -

web.servletExtensions=*.jsp

A web welcome file is described using the following syntax: -

web.welcomeFile=<relative filename>

A web sessionTimeout uses the following syntax: -

web.sessionTimeout=54

The web context root uses the following syntax: -

web.ContextRoot=northwind

War Packager (com.javelin.generator.packaging.WARPackager)

The WAR Packager is responsible for packing the War File.

The WAR Packager will package any files it finds under the web.pathName, with the extensions listed in the web.webExtensions property.

The war.webExtensions property is a space seperated list of file extensions. A full default list is provided in the default bdl file. It canbe changed .

For example: -

war.webExtensions=*.jsp *.html *.htm

A number of library jars can be packaged in the war. This is done using the following syntax.

war.libraryJars=[file[;file]

A list of files to deploy in the WAR jar can be given. A set of defaults is provided.

This allows specification of the path and the sub package within that path, using the following syntax: -

war.deployClasses.<index>=<path>,<package path>

For example: -

war.deployClasses.0=$ROOT/web/WEB-INF/classes,/com/javelin
war.deployClasses.1=C:/javelin/jbeans/src,com/javelin/beans

Ear Packager (com.javelin.generator.packaging.EarPackager)

The Ear Packager is responsible for bundling the library jars, the ejb jar and the war archives.

The ejb library files are added as a space seperated list as follows: -

ear.libraryJars=[file[;file]]

Abstract RI Writer (com.javelin.generator.packaging.ri,AbstractRIDeployer)

The AbstractRIDeployer is a super class that all RI writers extend.

The AbstractRIDeployer has the following methods: -

  • getEjbJarDescriptor() - get the vendor specific descriptor name.

 

RI Deployment Descriptor Writer (com.javelin.generator.packaging.ri.RIDeploymenDescriptorWriter)

This writer is responsible for writing the RI Deployment Descriptor.

If the ear contains any container managed beans the RI Deployment Descriptor Writer is responsible for writing vendor specific SQL to the descriptor.

RI Ear Packager (com.javelin.generator.packaging.ri.RIEarPackager)

This writer is responsible for adding the RI Deployment Descriptor to the Ear.

RI Undeployer (com.javelin.generator.packaging.ri.RIUndeployer)

This writer is responsible for uninstalling the ear from the RI application server.

RI Deployer (com.javelin.generator.packaging.ri.RIDeployer)

This writer for responsible for installing the ear to the RI application server.

Abstract WL Writer (com.javelin.generator.packaging.weblogic.AbstractWLDeployer)

The AbstractWLDeployer is a super class that all WL writers extend.

The AbstractWLDeployer has the following methods: -

  • getEjbJarDescriptor() - get the vendor specific descriptor name.

WL Deployment Descriptor Writer (com.javelin.generator.packaging.weblogic.WLDeploymenDescriptorWriter)

This writer is responsible for adding the Web Logic Deployment Descriptor to the Ear.

WL Ear Packager (com.javelin.generator.packaging.weblogic.WLEarPackager)

This writer is responsible for writing the Web Logic Deployment Descriptor.

If the ear contains any container managed beans the Web Logic Deployment Descriptor Writer is responsible for writing vendor specific SQL to the descriptor.

WL Undeployer (com.javelin.generator.packaging.weblogic.WLUndeployer)

This writer is responsible for uninstalling the ear from the Web Logic application server.

WL Deployer (com.javelin.generator.packaging.weblogic.WLDeployer)

This writer for responsible for installing the ear to the Web Logic application server.