Fix (APAR): PK71765 Status: Fix Release: 7.0 Operating System: AIX,HP-UX,i5/OS,IBM i,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,Solaris,Windows Supersedes Fixes: CMVC Defect: 546905 Byte size of APAR: 17100 Date: 2008-09-25 Abstract: The EJB deployment descriptor may have missing references. Description/symptom of problem: PK71765 resolves the following problem: ERROR DESCRIPTION:? The EJB deployment descriptor may have missing references when an EJB extends a base class containing EJB related annotations. This error will typically result in an injection failure. LOCAL FIX:? PROBLEM SUMMARY:? USERS AFFECTED: All users writing Java Platform, Enterprise Edition 5 applications containing Enterprise Java Bean (EJB) related annotations in non-EJB parent classes will be affected. PROBLEM DESCRIPTION: The EJB deployment descriptor may have missing references. RECOMMENDATION: None Annotations are a standard mechanism of adding metadata to Java classes. You can use metadata to simplify development and deployment of Java Platform, Enterprise Edition (Java EE) 5 artifacts. Prior to the introduction of Java language annotations, deployment descriptors were the standard mechanism used by Java EE components. These deployment descriptors were mapped to XML format, which facilitated their persistence. With WebSphere Application Server version 7, the Java EE 5 annotation-based metadata is merged with the existing XML-based deployment descriptor metadata. To avoid merging extraneous annotations, annotations from classes that happen to be in the archive but aren't part of the application, base classes and their annotations were excluded. This led to missing references in the EJB deployment descriptor when an EJB extends from a base class which contains EJB related annotations. PROBLEM CONCLUSION:? This issue was fixed by no longer filtering non-EJB base classes while continuing to screen out servlets, filters, etc. The fix for this APAR is currently targeted for inclusion in fixpack 7.0.0.1. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Install Fix to all WebSphere installations unless special instructions are included below. Special Instructions: None NOTE: The user must: * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V7.0.0.0 or newer of the Update Installer. Certain iFixes may require a newer version of the Update Installer and the Update Installer will inform you during the installation process if a newer version is required. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg24020212 1) The fix is delivered as a single file with a .pak extension (such as 7.0.0.1-WS-WAS-IFPK12345.pak). Copy the .pak file directly to the maintenance directory, /maintenance. 2) Shutdown WebSphere 3) For IBM i users, use the update command to install and uninstall the interim fix. The IBM Information Center can provide additional details, if needed, on the use of this command. http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=rins_update. For non-IBM i users, launch the Update Installer and click the Next button on the Welcome page. 4) Enter the directory path of the installation location of the WebSphere product you want to update, and click the Next button. 5) Select the "Install maintenance package" operation and click the Next button. 6) Enter the directory path of your maintenance directory where you have the maintenance packages (.pak files) and click the Next button. 7) The Available Maintenance Package to Install page should list all maintenance packages (.pak files) that it finds in the directory path provided in the previous step. The Update Installer will select the correct maintenance packages based on your system configuration and will not allow an invalid combination to be installed. Please keep the Update Installer recommendations and click the Next button and continue with the installation of the maintenance package. To determine why some maintenance packages have been identified as not applicable, see description in log found in /logs/tmp*/updatelogs.txt 8) For all platforms except Windows. In pre-install summary panel, use the "verify permission" feature to verify the user has permissions to apply updates to files associated with the selected maintenance. Correct any file permissions before clicking next to start the install. 9) Restart WebSphere Directions to remove fix: 1) Shutdown WebSphere 2) Start Update Installer 3) Enter the installation location of the WebSphere product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Select name of the maintenance package to uninstall (PKxxxxx.pak). 6) UnInstall maintenance package. 7) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere. Additional Information: