PM94953: APPLICATION CONTAINING A WEB FRAGMENT CANNOT BE DEPLOYED FROM A V8 DEPLOYMENT MANAGER TO A V7 APPLICATION SERVER

Fixes are available

APAR status

Closed as program error.

Error description

The deployment of an application fails when it is deployed
to a node running a version of WebSphere Application Server
that is lower than the version running on the deployment
manager.  The deployment fails when WebSphere Application
Server detects a web fragment inside the application and
upgrades the application to a version of Java EE not supported
on the node.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server deploying applications from a v8.0   *
*                  or v8.5 deployment manager node to a v7.0   *
*                  application server node.                    *
****************************************************************
* PROBLEM DESCRIPTION: Deployment of an application which      *
*                      contains fragment descriptors fails     *
*                      when the deployment is through a v8.0   *
*                      or v8.5 deployment manager node to a    *
*                      v7.0 application server node.           *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Deployment of an application through a v8.0 or v8.5 deployment
manager node to a v7.0 application server node fails when the
application contains any fragment descriptors
(META-INF/web-fragment.xml) in a jar file packaged within a
web module (WAR file).  The deployment fails because web
fragment descriptors are a feature of Java EE 6, which is
not supported by IBM WebSphere Application Server v7.0, and
because the IBM WebSphere Application Server deployment
processing tests the required Java EE level of an application
against the Java EE level which is supported by the target node
of the deployment.
Deployment of the application is successful when performed
through a v7.0 deployment manager node because v7.0 nodes do
not detect fragment descriptors: IBM WebSphere Application
Server v7.0 implements Java EE 5 and has no knowledge of web
fragment descriptors, which are a feature of Java EE 6 /
Servlet 3.0.

Problem conclusion

This APAR adds a custom property and manifest attribute which
cause web fragment descriptors to be ignored.

To ignore web fragment descriptors in all applications which
are deployed through a deployment manager node, set the
following java custom property:

org.eclipse.jst.j2ee.commonarchivecore.ignore.web.fragment=true

To ignore web fragment descriptors in all modules of an
application, set the following manifest attribute in the
application level manifest file (META-INF/MANIFEST.MF) of the
application:

Ignore-Web-Fragment: true

To ignore the web fragment descriptor in a single module, set
the manifest attribute in the module level manifest file.

Adding the manifest attribute is preferred over setting the
java custom property, since the custom property applies to all
application deployments made through the deployment manager
node, while the manifest attribute is specific to deployments
of the  application or application module.

Both the custom property and the manifest attribute are
intended to enable deployment of applications which contain
web fragment descriptors through a v8.0 or v8.5 deployment
manager node to a v7.0 application server node.  The property
and attribute are only appropriate for cross level
deployments.  Unpredictable results will occur when the
property or attribute are used for deployments to a v8.0
or v8.5 node.

This APAR addresses only the case of fragment descriptors.
Other features of the application, for example, annotations
which are new to Java EE 6, EJB content in web modules, and
managed beans content in all modules, are not addressed by
this APAR.

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
PM94953
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-08-12
Closed date
2013-08-28
Last modified date
2014-03-20

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

PM94953: APPLICATION CONTAINING A WEB FRAGMENT CANNOT BE DEPLOYED FROM A V8 DEPLOYMENT MANAGER TO A V7 APPLICATION SERVER

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?