Bug 779858 (SOA-2218)

Summary:	SOAPClient action remappes objects with null strings to empty strings
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Jiri Pechanec <jpechane>
Component:	JBossESB	Assignee:	Kevin Conner <kevin.conner>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2 GA	CC:	kevin.conner
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-2218
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	779859 (view as bug list)		Environment:
Last Closed:	2011-02-18 01:39:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jiri Pechanec 2010-08-10 14:52:06 UTC

project_key: SOA

See JBESB-3451

Comment 1 Kevin Conner 2010-08-10 14:58:52 UTC

Link: Added: This issue depends JBESB-3451

Comment 2 Kevin Conner 2010-08-10 16:36:07 UTC

Link: Added: This issue is incorporated by SOA-2210

Comment 3 Laura Bailey 2010-12-17 00:41:28 UTC

Writer: Added: Darrin

Comment 4 Laura Bailey 2010-12-17 00:47:55 UTC

Release Notes Docs Status: Added: Not Yet Documented

Comment 6 Jiri Pechanec 2011-01-07 07:25:11 UTC

Verified in ER6

Comment 7 Kevin Conner 2011-02-17 13:55:37 UTC

The SOAPClient always mapped null objects to an empty element, this has been changed so that it can can also choose the xsi:nil attribute if appropriate.

Comment 8 Dana Mison 2011-02-18 01:39:13 UTC

Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue
Release Notes Text: Added: The SOAPClient always mapped null objects to an empty element.  This has been changed so you also have the option to use the xsi:nil attribute if appropriate.