A fix is available
APAR status
Closed as program error.
Error description
NOTE: APAR 42012 FIX PACKAGE WAS REPLACED ON May 18 2012 TO FIX REGRESSION AND PACKAGING ISSUES. DETAILS IN APAR JR42860. Example - complexType CzWs03TntfUser In this type there is an element 'caller' . This attribute is nillable and his type is complexType Czws03tntfTcallerUser. We want to call Web Service cz_ws03_stntf. This WS has 1 parameter stntfElement. We set parameters storetype and notification in stntfElement. Since we have no information about caller, so we don't need to set this attribute in notification (CzWs03TntfUser). But we must set all attributes in caller (default values like 0 or empty string), because nillable (true) elements are not handled properly. By specification if you specify a nillable=true and do not initialize the variable then it should return something like: <ns1:inputParam xmlns:ns2="http://www.w3.org/2001/XMLSchema-instance" ns2:nil="true"/> (notice the "nil=true" but in BPM it does not return "nil=true") For example if you want to send only <items /> element but instead will need to send <items> <amount/> <name/> <something/> ..... </items> because nillable (true) elements are not handled properly. The exception that is thrown is: Caught exception while handling request: unexpected element name: at org.apache.axis.message.SOAPFaultBuilder.createFault After applying this fix there is a chance you can run into the issue documented in JR44953 if you have previously applied an IFix for JR43231.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: Users of BPM Express, BPM Standard and BPM * * Advanced. * **************************************************************** * PROBLEM DESCRIPTION: Teamworks Web Service connector does * * not honor nillable=true attribute. * * For example if you want to send only * * an * * <items/> element but * * instead you will need to send * * <items> * * <amount/> * * <name/> * * <something/> * * ..... * * </items> * * because nillable (true) elements are * * not handled properly. * **************************************************************** * RECOMMENDATION: Ifix is Recommended * **************************************************************** Teamworks Web Service connector does not honor nillable=true attribute. For example if you want to send only <items /> element but instead you will need to send <items> <amount/> <name/> <something/> ..... </items> because nillable (true) elements are not handled properly. The exception that is thrown is: Caught exception while handling request: unexpected element name: at org.apache.axis.message.SOAPFaultBuilder.createFault
Problem conclusion
NOTE: APAR 42012 FIX PACKAGE WAS REPLACED ON May 18 2012 TO FIX REGRESSION AND PACKAGING ISSUES. DETAILS IN APAR JR42860. The problem was fixed by adding a 'isNillable()' if found null. Following is the correct behaviour after the fix: If the Advanced Parameter Properties value for Nillable is true, the element in the WSDL will be generated with the nillable attribute set to "true". If Nillable is set to <default> or false, the element in the WSDL will be generated without the nillable attribute set. Per the W3C XML Schema specification if the nillable attribute is not present, it will be considered false. The fix is available in IFIX JR42012 on fixcentral http://www-933.ibm.com/support/fixcentral/ and needs to be installed as follows: 1. Install JR42012 on both Process Designer and Process Center/Server using IM 2. On Process Center/Server run "bpmprofileUpgrade" only: For Standalone: http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/topic/c om.ibm.wbpm.imuc.doc/topics/tmig_upgrading_bpm_errors.html (step 2 only in above link) For Clusters, only Step 3 in: http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/topic/c om.ibm.wbpm.imuc.doc/topics/tmig_upgrading_bpm_nd_clusters.html (RUN only step 3 and has to be run on all clusters) >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> JR42012 also contains the following fixes: http://www-01.ibm.com/support/docview.wss?uid=swg1JR41344 http://www-01.ibm.com/support/docview.wss?uid=swg1JR41658 http://www-01.ibm.com/support/docview.wss?uid=swg1JR41473 http://www-01.ibm.com/support/docview.wss?uid=swg1JR41755 http://www-01.ibm.com/support/docview.wss?uid=swg1JR41554 http://www-01.ibm.com/support/docview.wss?uid=swg1JR41725 http://www-01.ibm.com/support/docview.wss?uid=swg1JR41381 http://www-01.ibm.com/support/docview.wss?uid=swg1JR41469 http://www-01.ibm.com/support/docview.wss?uid=swg1JR41928 http://www-01.ibm.com/support/docview.wss?uid=swg1JR41917 http://www-01.ibm.com/support/docview.wss?uid=swg1JR41994 http://www-01.ibm.com/support/docview.wss?uid=swg1IC81614 http://www-01.ibm.com/support/docview.wss?uid=swg1JR42100 http://www-01.ibm.com/support/docview.wss?uid=swg1JR42113 http://www-01.ibm.com/support/docview.wss?uid=swg1JR42192 http://www-01.ibm.com/support/docview.wss?uid=swg1IC79732 http://www-01.ibm.com/support/docview.wss?uid=swg1JR42110 Please check individual fix links for details.
Temporary fix
Comments
APAR Information
APAR number
JR42012
Reported component name
BPM STANDARD
Reported component ID
5725C9500
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-02-22
Closed date
2012-04-17
Last modified date
2012-11-29
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
BPM STANDARD
Fixed component ID
5725C9500
Applicable component levels
R750 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5"}]
Document Information
Modified date:
07 October 2021