Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 363197

Summary:

@XmlElementWrapper - Empty collections and nillable property

Product:

z_Archived

Reporter:

Blaise Doughan <blaise.doughan>

Component:

Eclipselink

Assignee:

Nobody - feel free to take it <nobody>

Status:

RESOLVED FIXED

QA Contact:

Severity:

normal

Priority:

CC:

blaise.doughan, david.mccann, rick.barkhouse

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
WIP	none
WIP	none
Work in progress	none
Work in progress	none
Work in progress	none
Work in progress	none
Work in progress	none
WIP - re-based on 2.3	none
Patch - code changes - 2.3	none
Patch - test changes - 2.3	none
Patch - test changes - 2.3	none
Patch - test changes - 2.3	none
Patch - code changes - 2.3	none
Patch - code changes - 2.4	none
Work in progress	none
Patch - Code changes	none
Patch - Test changes	none
Patch - test changes	none
Patch - code changes	none

Description Blaise Doughan

2011-11-08 11:42:33 EST

Empty Collections

For fields/properties annotated with @XmlElementWrapper if the collection is empty the wrapper element should be marshalled out.  This is done by JAXB to differentiate between null and empty collections.

Nillable

If the field/property is annotated with @XmlElementWrapper(nillable=true) and the collection is null, then the wrapper element should be marshalled with xsi:nil="true".

Comment 1 Rick Barkhouse

2011-11-11 12:40:44 EST

Created attachment 206865 [details]
WIP

Comment 2 Rick Barkhouse

2011-11-11 16:18:21 EST

Created attachment 206876 [details]
WIP

Comment 3 Rick Barkhouse

2011-11-14 14:16:27 EST

Created attachment 206978 [details]
Work in progress

Comment 4 Rick Barkhouse

2011-11-14 14:20:07 EST

Created attachment 206979 [details]
Work in progress

Comment 5 Rick Barkhouse

2011-11-14 14:21:19 EST

Created attachment 206980 [details]
Work in progress

Comment 6 Rick Barkhouse

2011-11-14 14:29:39 EST

Created attachment 206983 [details]
Work in progress

Comment 7 Rick Barkhouse

2011-11-15 16:41:12 EST

Created attachment 207059 [details]
Work in progress

Comment 8 Rick Barkhouse

2011-12-16 17:01:07 EST

Created attachment 208512 [details]
WIP - re-based on 2.3

Comment 9 Rick Barkhouse

2011-12-19 15:23:58 EST

Created attachment 208580 [details]
Patch - code changes - 2.3

Comment 10 Rick Barkhouse

2011-12-19 15:24:26 EST

Created attachment 208581 [details]
Patch - test changes - 2.3

Comment 11 Rick Barkhouse

2011-12-19 15:26:42 EST

Created attachment 208582 [details]
Patch - test changes - 2.3

Comment 12 Rick Barkhouse

2012-01-16 13:27:33 EST

Created attachment 209576 [details]
Patch - test changes - 2.3

Comment 13 Rick Barkhouse

2012-01-16 13:27:53 EST

Created attachment 209577 [details]
Patch - code changes - 2.3

Comment 14 Rick Barkhouse

2012-01-16 13:29:46 EST

Created attachment 209578 [details]
Patch - code changes - 2.4

Comment 15 Rick Barkhouse

2012-01-24 16:54:10 EST

Created attachment 210016 [details]
Work in progress

Comment 16 Rick Barkhouse

2012-01-27 16:06:34 EST

Created attachment 210222 [details]
Patch - Code changes

Comment 17 Rick Barkhouse

2012-01-27 16:06:55 EST

Created attachment 210223 [details]
Patch - Test changes

Comment 18 Rick Barkhouse

2012-01-30 13:47:44 EST

Created attachment 210274 [details]
Patch - test changes

Comment 19 Rick Barkhouse

2012-01-30 13:47:58 EST

Created attachment 210275 [details]
Patch - code changes

Comment 20 Rick Barkhouse

2012-01-30 14:25:04 EST

Checked into trunk, waiting for bug 368863 to go into 2.3 before backporting this.

Comment 21 Rick Barkhouse

2012-02-03 09:57:48 EST

Checked into 2.3.3 as well.

Comment 22 Blaise Doughan

2012-05-15 15:55:50 EDT

*** Bug 291406 has been marked as a duplicate of this bug. ***

Comment 23 Eclipse Webmaster

2022-06-09 10:28:23 EDT

The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink