APAR status |
Closed as program error.
| Error description
The problem is the import does not set an "EMPTY" state when
importing the EJB for the datasource attribute, so when you do
an export it complains that it is missing. Local fixProblem summary
****************************************************************
* USERS AFFECTED: All users of XMLConfig for WebSphere *
* Application Server 3.5.6 release. *
****************************************************************
* PROBLEM DESCRIPTION: Problem with XMLConfig import of EJB *
* model with no <data-source> element, *
* database is not properly updated to *
* contain an empty element. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The XMLConfig import is not setting the "EMPTY" state when
importing the EJB for the data source attribute, so when you
do an export it complains for the missing attribute. Also the
same is happening for Container object. Problem conclusion
Fixed code in EJBConfig.java and ContainerConfig.java files. Temporary fix
pq61516.jar Comments
APAR information | APAR number | PQ61516 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2002-05-23 | Closed date | 2002-06-17 | Last modified date | 2002-06-17 |
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 APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED AI | Fixed component ID | 5648C8400 |
Applicable component levels | R350 PSY | UP |
|