PQ51087: CANNOT GENERATE DEPLOYED CODE WITH WLM FOR EJBS IN PACKAGE JAVA.* OR JAVAX.*


APAR

APAR status
Closed as fixed if next.

Error description
WebSphere Application Server Advanced 3.5.3 All Platforms
Cannot generate deployed code with WLM for EJBs in package
java.* or javax.*

For EJBs whose package name begins with java.* or javax.*, the
rmic compiler generates the stubs in package org.omg.stub.java.*
(or org.omg.stub.javax.* ), as per the RMI-IIOP specification.
The EJB's remote and home interface remains in the original
java.* or javax.* package.

In WAS 3.5.3,  wlmsg (WLM stub generator) does not account for t
stubs and EJB interfaces being in different packages. This manif
differently in VisualAge for Java and WebSphere.
n VisualAge for Java, the package name that is passed to wlmsg
is org.omg.stub.java.* (or org.omg.stub.javax.* ), and the inter
name is passed without the package prefix. This is in compliance
with the wlmsg help:

Usage: java wlmsg [options]<RemoteInterfaceName>
Options:with the wlmsg help:Usage: java wlmsg [options]
-help displays this message -dir <dirName> directory for input and output files -src <dirName> source directory for input files -p <pkgName> package name for stubs and ties -name<name> name of stub without the rmic-added prefix or suffix: required (-if is the same) -idl for working with idl stubs -trace<traceSpec> trace spec For example, if the EJB MyBean is in package javax.test, the -p (pkgName) argument passed is package name passed is org.omg.stub.javax.test, and the RemoteInterfaceName passed in is MyBean. Code generation fails with this error in the log:Options:-help displays this message, -dir, directory for input and outputfiles, -src, source directory for input files, -p, package name for stubs and ties-name, name of stub without the rmic-addedprefix or suffix: required (-if is the same)-idl for working with idl stubs-trace, trace specFor example, if the EJB MyBean is in package javax.test, the -p(pkgName) argument passed is package name passed isorg.omg.stub.javax.test, and the RemoteInterfaceName passed
Error during WLM stub generation:in is MyBean. Code generation fails with this error in the log:
java.lang.ClassNotFoundException: Class org.omg.stub.javax.test.MyBean not found! Since you cannot disable WLM stub generation in VAJ, this result in failure to complete code generation. Any combination of packa name and remote interface name fails. WebSphere Application Server 3.5.3 In WAS 3.5.3, when deploying ejbs with WLM enabled, the package name passed to wlmsg is the EJB's package name. (javax.*) This fails due to the stub not being found , with this exception:Error during WLM stub generation:java.lang.ClassNotFoundException: Classorg.omg.stub.javax.test.MyBean not found!Since you cannot disable WLM stub generation in VAJ, this resultin failure to complete code generation. Any combination of packaname and remote interface name fails.WebSphere Application Server 3.5.3In WAS 3.5.3, when deploying ejbs with WLM enabled, the packagename passed to wlmsg is the EJB's package name. (javax.*) This
com.ibm.ejs.sm.exception.DeploymentException The tracefile error is:fails due to the stub not being found , with this exception:com.ibm.ejs.sm.exception.DeploymentException
[01.06.29 10:54:06:906 EDT] 1294da2a WLMStubGenera W Class "javax.test"."_Bean1_Stub" not found
The tracefile error is:[01.06.29 10:54:06:906 EDT], 1294da2a WLMStubGenera W Class"javax.test"."_Bean1_Stub" not found
Local fix
There is no local fix.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere 3.5 users of WLM with EJBs in      *
*                 java.* or javax.*                            *
****************************************************************
* PROBLEM DESCRIPTION: Can't generate deployed code if EJBs    *
*                      in one of the above                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This problem has been corrected in WAS4.0 AE.  The suggested
work around is to move the user code out of the javax package.
Problem conclusion
Temporary fix
Comments
APAR information
APAR numberPQ51087
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED FIN
PENoPE
HIPERNoHIPER
Submitted date2001-07-31
Closed date2001-08-24
Last modified date2001-08-24

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros

Fix information
APAR is sysrouted TO one or more of the following:Modules/Macros

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ51087
IBM Group: Software Group
Modified date: 2001-08-24