PQ67453: DIFFERENT PACKAGES FOR HOME/REMOTE INTERFACES & BEAN FAILS

 Fixes are available

EJB Container; 4.0.2-4.0.7: Component Cumulative fix for EJB Container
4.0.5: WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)



APAR status
Closed as program error.

Error description
While developing an EJB as follows
1. Home interface in the home package.
 2. Remote interface in the remote package.
 3. Bean implementation in the bean package.
The home, remote and bean are 3 different packages.
Running "generate deploy and RMIC code" in either WSAD 4.0.3
or WAS AE 4.0.2 completes successfully but when trying to start
the EJB Server which in turn loads the bean, the exception:
  java.io.FileNotFoundException
The EJSRemoteStatelessPkgTestHome.java and its stub
_EJSRemoteStatelessPkgTestHome_Tie.java are generated in the
remote package and EJB server searches for it in the hom
package.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users who       *
*                 implement EJB's using different packages for *
*                 remote and home interfaces.                  *
****************************************************************
* PROBLEM DESCRIPTION: If an EJB implementation uses           *
*                      different packages for remote and home  *
*                      interfaces, this bean will fail to      *
*                      start in the application server with    *
*                      a FileNotFoundException.                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If an EJB uses different packages for remote and home
interfaces, EJB Container looks for theses classes in the
incorrect location and subsequently failed to start the bean
in the application server.
Problem conclusion
During the start bean process, the EJB container attempts to
load the bean class from the incorrect package and hence the
FileNotFoundException is thrown.

This APAR corrects the package name of the class to be loaded
in the WebSphere Application Server.
Temporary fix
\\wasdoc0\WAS_EJBContainer_cumulative_eFixes
Comments
Please request the customer to remove any previous fix in
the %WAS_HOME%\classes subdirectory before apply the new
eFix to their configuration.

The current eFix can be found from:

\\wasdoc0\WAS_EJBContainer_cumulative_eFixes

Once the customer verifies this cumulative eFix works for
them, this will promoted to become the official EJB
container eFix for 4.0.2 to 4.0.4.
APAR information
APAR number PQ67453
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-10-21
Closed date 2002-11-19
Last modified date 2002-11-19

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
EJBCONTR          

SRLS

Fix information
Fixed component name WEBSPHERE AE NT
Fixed component ID 5630A2201

Applicable component levels
R400 PSY    UP


Document Information


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