PK73302: VALIDATION FOR JAX-WS APPLICATION FAILED DURING EDIT TASK.

Fixes are available

APAR status

Closed as program error.

Error description

JAX-WS enterprise bean jar and its router module(s), the
servlet war(s), can be deployed onto different targets. As a
result, applications may not work properly after deployment.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
****************************************************************
* PROBLEM DESCRIPTION: JAXWS enterprise bean module            *
*                      validation logic was not working        *
*                      properly during application edit. For   *
*                      example, JAXWS enterprise bean and its  *
*                      router module(s) were allowed to        *
*                      deploy onto different target servers.   *
*                      No exception or warning was being       *
*                      thrown. As a result, the application    *
*                      did not work properly after deployment. *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Enterprise bean router validation does not work for JAX-WS
services during application edit. The JAX-WS enterprise bean
module and its router modules (WAR or JMS) should be targeted
to the same servers. When they are targeted to different
servers, an error should be reported. But currently there is
no error reported. The problem only happens during application
edit (after the application is installed).

Problem conclusion

In CommonUtils.java. before this fix, the code searches for the
serviceIndex.xml file under the WEB-INF directory ONLY. As we
know the serviceIndex for the enterprise bean jar should be
under the META-INF directory.
To address this issue, the code now searches the META-INF
directory  first, then does the previous old logic by searching
the WEB-INF directory, for the serviceIndex.xml file.

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

Temporary fix

Comments

APAR Information

APAR number
PK73302
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-10-06
Closed date
2008-10-29
Last modified date
2008-11-14

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 October 2021

Tips

PK73302: VALIDATION FOR JAX-WS APPLICATION FAILED DURING EDIT TASK.

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

R700 PSY

Document Information

Share your feedback

Need support?