PK20762: WHEN A JAX-RPC HANDLER IS DEPLOYED TO A WSGW SERVICE GETLOCALNAME AND GETQUALIFIEDNAME RETURN BLANK.

 Fixes are available

5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Solaris
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Windows
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Windows
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for AIX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for HP-UX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for AIX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Linux
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for HP-UX
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Linux
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Solaris
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Windows
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for HP-UX
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for AIX
5.0.2.18: WebSphere Application Server 5.0.2 Cumulative Fix 18 for Linux
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Solaris



APAR status
Closed as program error.

Error description
When a JAX-RPC handler is deployed to a WSGW service on its
target service side, it seems that both
element.getElementName().getQualifiedName() and
element.getElementName().getName() return a blank string because
the element data is held by the Web Service Engine in an
alternate content format. This should probably be recognized
that the element data is in an alternate format in this
situation when these calls are made and returning the correct
string information (rather than "").
Local fix
However, various workarounds do exist and these are as follows:
1.  A JAX-RPC handler deployed to a WSGW service on its
SOAP/HTTP channel side does not seem to exhibit the problem so
this may represent a valid alternative to that which is failing.

2.  If it is essential that the information be made available to
a WSGW-deployed JAX-RPC handler on the target-service side, the
information can be read by the channel-side handler and passed
to target-service side handler in the MessageContext using
handler-defined properties.

3.  If the WSGW service is deployed with selective soap parsing
enabled and the application server configured with Application
classloader policy set to Single (which is essential for
selective soap parsing operation) then the problem should not
occur.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server version 5       *
*                 web services users                           *
****************************************************************
* PROBLEM DESCRIPTION: When a JAX-RPC handler is deployed to   *
*                      a WSGW service ,                        *
*                      soapelement.getelementname().           *
*                      getlocalname() and                      *
*                      soapelement.getelementname().           *
*                      getqualifiedname() return blank.        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the WSGW component invokes the Web Services component
with a null value, Web Services is unable to catch this
condition and does a no-op for it.
Problem conclusion
To fix this problem,an extra condition statement was added to
catch the null value call and to deserialize the data to
something that will be returned back to the call from WSGW
handler.

This APAR will be included in the following cumulative fixes:
5.0.2.17
5.1.1.10
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 PK20762
Reported component name WAS NETWRK DEPL
Reported component ID 5630A3601
Reported release 10W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2006-03-02
Closed date 2006-03-21
Last modified date 2006-03-21

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
WEBSERVI          

Publications Referenced

Fix information
Fixed component name WAS NETWRK DEPL
Fixed component ID 5630A3601

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00S PSY    UP
R00W PSY    UP
R103 PSY    UP
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10S PSY    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 10W
Software edition:
Reference #: PK20762
IBM Group: Software Group
Modified date: Mar 21, 2006