PK82768: JAX-WS THINCLIENT OSGI NOT LOADING PROPERLY

Fixes are available

APAR status

Closed as program error.

Error description

When the JAX-WS thin client is used to invoke a web service
within an OSGi environment, the IBM implementations of JAX-B
and JAX-WS are not being used.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All IBM WebSphere Application Server V7.0   *
*                  users of the JAX-WS thin client within an   *
*                  OSGi environment                            *
****************************************************************
* PROBLEM DESCRIPTION: When using a JAX-WS thin client         *
*                      within an OSGi environment, the IBM     *
*                      JAX-WS and JAX-B implemenations are     *
*                      not used.                               *
****************************************************************
* RECOMMENDATION:  Install a fixpack that contains this APAR.  *
****************************************************************
A customer in an OSGi environment can use the IBM Thin Client
for JAX-WS (JAX-WS thin client) by importing the thin client
into their application's manifest file.

For example, the customer will have the following in their
manifest file:
    Require-Bundle: com.ibm.wsfp.thinclient

In such cases, the customer expects that the application will
use the IBM versions of JAX-WS and JAX-B.  Instead, OSGi is
loading the default implementations of JAX-WS and JAX-B.

This may result in unexpected errors.

Problem conclusion

The JAX-WS thin client is fixed to correctly export the
META-INF services.  The IBM factory settings are now
visible to users within an OSGi environment.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.5.  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
PK82768
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
2009-03-17
Closed date
2009-04-02
Last modified date
2009-04-02

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:
24 October 2021

Tips

PK82768: JAX-WS THINCLIENT OSGI NOT LOADING PROPERLY

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?