PM90887: ANNOTATION FILTER PROPERTIES NOT WORKING FOR MODULE VERSIONING

Fixes are available

APAR status

Closed as program error.

Error description

Annotations filter properties are not enabled for steps which
scan modules for content and which determine whether the
enclosing application can be deployed to a V7.0 node.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server who are using Java archive or Java   *
*                  package filters to improve annotation       *
*                  processing performance.                     *
****************************************************************
* PROBLEM DESCRIPTION: WebSphere Application Server code       *
*                      that scans jar files to determine       *
*                      module types does not honor the         *
*                      filters specified by the user.  Jars    *
*                      and packages which are specified to     *
*                      be skipped during annotations           *
*                      processing are still scanned when       *
*                      determining module types.               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Three problems result: First, the full potential performance
benefit of specifying annotation filters is not realized.
Second, module typing will detect annotations which are
ignored by other annotation processing steps, leading to
inconsistent deployment results.  Third, because the module
typing results are used to identify the Java EE support level
required by the application, annotation filters are not
effective for enabling deployment of applications through a
v8.0 (or higher) Deployment Manager node to a v7.0 Application
Server node.
Module types must be identified when the Enterprise
Application Archive (EAR file) does not contain an application
deployment descriptor, META-INF\application.xml, and when
module deployment descriptors are not metadata complete.
Java EE support requirements are determined based on the
presence of annotations requiring a particular Java EE level,
and based on the presence of EJB content in web modules
(WAR files), and based on the presence of managed
beans content in both EJB Jar and WAR files.

Problem conclusion

The code that determines module types has been updated to
honor the annotation filters.

The fix for this APAR is currently targeted for inclusion in
fix packs 8.0.0.8 and 8.5.5.2.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM90887
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-06-11
Closed date
2013-08-27
Last modified date
2013-08-28

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

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R800 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022

Tips

PM90887: ANNOTATION FILTER PROPERTIES NOT WORKING FOR MODULE VERSIONING

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?