PQ85043: SOAPFAULT RETURNS COMPLEXTYPE NAME INSTEAD OF THE ELEMENT NAME | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer has a soap app that contains a complextype named SoapFault with an element named soapFault . Customer is running the same app on both Distributed WebSphere at the 5.0.2.3 level and zOS WebSphere at the W502000 level. Distributed WebSphere returns the element name ( soapFault ) but zOS WebSphere returns the Complextype ( SoapFault ) . Customer requires the zOS WebSphere to be consistent with distributed WebSphere on his NT system.Local fix HBCProblem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: SoapFault returns incorrect * * soap fault message. The ElementName * * and ComplexType tags are in the wrong * * locations. * **************************************************************** * RECOMMENDATION: * **************************************************************** SoapFault uses the name of the Complextype, not the actual element name. External symptom: SoapFault returns the following: <ElementName> <ComplexType>... </ComplexType> </ElementName> Correct response should be: <ComplexType> <ElementName> ... </ElementName> </ComplexType>Problem conclusion Webservices is now equivalent to WAS Distributed 5.02.3. The following apars have been resolved: PQ85640 A HANDLEFAULT METHOD INVOCATION IS MISSING FOR A WEB SERVICES PQ76837 CLASSCASTEXCEPTION ON V5.0.1 WHEN WEBSERVICES INVOKES JSP PQ77329 Re-starting an EAR more than once causes an EJB Web Service PQ77329.2 Data cached for one app not appropriate for another application PQ78168 Multi-threaded web service fails occasionally PQ78554 ClassCastException when roles assigned to handlers in webservices.xml or client service-ref. PQ79201 SOAPELEMENT IS NOT SERIALIZABLE AND CANNOT BE USED IN AN EJB PQ79383 NULLPOINTEREXCEPTION IS THROWN WHEN RUNNING PQ79428 WSAS 5.0.2 JAX-RPC WebService getting reply tag twice PQ80448 Generated stubs should not call JavaUtils. PQ80568 doc/lit wrapped array param ser'd wrong PQ80854 InternalException when default package is used. PQ80393 no attachment carried for soapconnection PQ80683 Namespace context not used in selective parsing PQ81647 xsd:any should be sent over the wire w/o wrapper PQ82076 WSDL2Java -noDataBinding does not generate compatible codes PQ80111 deserialization problems with SOAPElement types PQ80391 Need to release workspace in URLPatternHolder.remo PQ80448 Generated stubs should not call JavaUtils. PQ80568 doc/lit wrapped array param ser'd wrong APAR PQ85043 is associated with SERVICE LEVEL W502008 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ85043.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ85043
IBM Group: Software Group
Modified date: Jun 3, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.