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

Bug 362329

Summary:

Complex type name for arrays is based on Java rather than schema name

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:

eclipselink.oxm-inbox

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
MOXy - Test Cases	none
MOXy - Fix (2.3.2)	none
MOXy - Fix (trunk)	none
MOXy - Fix (2.3.2)	none
MOXy - Fix (trunk)	none

Description Blaise Doughan

2011-10-28 11:45:53 EDT

Currently when we build a JAXBContext on an array type (i.e. BigInteger.class) the corresponding complex type is based on the class (bigIntegerArray) instead of the schema type (integerArray).

Comment 1 Blaise Doughan

2011-10-28 12:04:22 EDT

Created attachment 206138 [details]
MOXy - Test Cases

Comment 2 Blaise Doughan

2011-10-28 12:04:49 EDT

Created attachment 206140 [details]
MOXy - Fix (2.3.2)

Comment 3 Blaise Doughan

2011-10-28 12:05:08 EDT

Created attachment 206141 [details]
MOXy - Fix (trunk)

Comment 4 Blaise Doughan

2011-10-28 14:54:47 EDT

Created attachment 206148 [details]
MOXy - Fix (2.3.2)

Comment 5 Blaise Doughan

2011-10-28 15:08:32 EDT

Created attachment 206149 [details]
MOXy - Fix (trunk)

Comment 6 Blaise Doughan

2011-10-28 15:16:17 EDT

Fix checked into 2.3.2 at rev:  10295
Fix checked into trunk at rev:  10296

Code reviewed by:  Denise Smith

Fix details:
Changed complex type name for array to be based on XML rather than Java type.

Comment 7 Eclipse Webmaster

2022-06-09 10:24:32 EDT

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