PQ57752: WAS 4.0 INFOCENTER, LOOSE CLASS FILES AT EAR LEVEL NON-SUPPORTED

APAR status
Closed as documentation error.

Error description
Single .class files are not supported within the files section
at the ear level in WAS 4.0x.
This is documented to be possible in the WAS 4.0 infocenter
section 6.6.24.0 and has an example.
The tool that picks up these parameters and generates deployment
code, EJBDeploy, does not have the ability to use loose class
files.
At this point the documentation needs to be changed until the
functionality is available.
Local fix
These loose .class files can be packages in a module or placed
into a jar at the ear level and the jar referenced in the
classpath of the module that needs it.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of the    *
*                 EJB deploy tool.                             *
****************************************************************
* PROBLEM DESCRIPTION: Loose class files using the Class-Path  *
*                      setting are not supported.              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The problem is section 6.6.24.0
.
It looks like it was copied (more or less) from the Sun spec
for jar manifests.  More or less, because it has an error
(Classpath should be Class-Path) and it is not clear.
.
The key point is the following:
.
The J2EE standard lets you identify loose class files using
the Class-Path setting. Specifically, you identify a directory,
and any .class files in the directory will be used.
.
The WebSphere documentation erronously copied this. WebSphere
does not support this. All class files must be packaged in jar
files.
.
The user needs to do the following:
.
- for each EJB jar file in the ear file, all the dependent
  classes must be in jar files contained within the ear file.
  The manifest file for a particular jar must identify the jars
  which contain the dependent classes. It does this using the
  Class-Path (as described in 6.6.24.0).
- if the dependent classes are not in jars already included in
  the ear, and are loose class files, they must be packaged
  into a jar, that jar must be included in the ear, and the EJB
  jar that needs these classes must identify this jar in its
  Class-Path.
Problem conclusion
Closing as a documentation change.
Temporary fix Comments
APAR information
APAR number PQ57752
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED DOC
PE NoPE
HIPER NoHIPER
Submitted date 2002-02-12
Closed date 2002-04-01
Last modified date 2002-04-01

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

Applicable component levels


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ57752
IBM Group: Software Group
Modified date: Apr 1, 2002