Multiple Jar File Architecture

This section describes working with the multiple jar file architecture.

The following topics are discussed:

UseBean Tag Changes

This section describes the useBean tag and the newInstance method.

Use the newInstance method to instantiate Business types and Relationship types classes rather than the useBean tag when only page or request scope is required. This allows full use of the mapping files and type hierarchy lookup to obtain the appropriate object instance. The newInstance method cannot be used to instantiate classes from the ui, taglib, or util packages, or any helper classes that do not represent a Business or Relationship type.

The use of the newInstance method insulates your code from any reorganization of jar files that may happen. The newInstance method works off a mapping file that will be adjusted to point to the correct class.

New Up Classes

At no time should any Java code new up a Business or Relationship type object directly. The newInstance method must be used in these cases.

Fully-qualified Class References

There may be places in existing Java code where references are made to fully-qualified class names. Typically, these occur when referencing static methods. These areas should be modified to use the current packaging.

There may also be places in Java code where you directly new up instances of non-Business or Relationship type classes. These areas also should be modified to use the current packaging.

Tag Library

The tag library descriptor (tld) file named "component.tld." is referenced in all JSPs by a common include file that defines the tld source and available prefixes ("framework", "fw", and "emxUtil"). The fw and emxUtil prefixes have been removed, so you should use the framework prefix on any JSP extensions.

ENOVIA Business Process Services offers the common include file named emxTagLibInclude.inc that each application then includes in one of their common include files using: 

<%@include file = "../emxTagLibInclude.inc"%>