PM11171: In a JAX-WS ibm-webservicesclient-bnd.xmi file, the componentNameLink attribute may refer to an incorrect bean

Fixes are available

APAR status

Closed as program error.

Error description

When an application does not have an
ibm-webservicesclient-bnd.xmi in its EAR file, the file is
automatically generated when deployed. The generated
ibm-webservicesclient-bnd.xmi file is used for
the overriddenEndpointURI property.

When there are more than one EJB beans in the application JAR
file, the componentNameLink attribute may refer to an incorrect
bean name.  As the result, when accessing Enterprise
Applications -> <application_name> -> Manage Modules ->
<JAR_module> -> Web services client bindings page from the
Administrative Console, the EJB field displays an incorrect bean
name.

This happens only for JAX-WS Web services.

Local fix

```
none at this time
```

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V7.0 users *
*                  of JAX-WS applications with @WebServiceRef  *
*                  annotations.                                *
****************************************************************
* PROBLEM DESCRIPTION: In ibm-webservicesclient-bnd.xmi        *
*                      file, the componentNameLink attribute   *
*                      may refer to an incorrect bean name.    *
****************************************************************
* RECOMMENDATION:  Install a fixpack containing this APAR.     *
****************************************************************
In an ibm-webservicesclient-bnd.xmi file, the componentNameLink
attribute may refer to an incorrect bean name.

Problem conclusion

The Web services engine scans and processes the
@WebServiceRef annotation and uses the information when
generating the ibm-webservicesclient-bnd.xmi
file.  When there are multiple beans in the application JAR,
an incorrect EJB bean name may be used as the componentNameLink
attribute value.

The Web services engine code has been fixed so that the correct
EJB bean name is used for componentNameLink attribute.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.13.  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
PM11171
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
2010-03-30
Closed date
2010-04-19
Last modified date
2010-04-19

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

Tips

PM11171: In a JAX-WS ibm-webservicesclient-bnd.xmi file, the componentNameLink attribute may refer to an incorrect bean

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?