different unmarshalling behavior between primitive type and simpletype with enumeration under restriction

[glassfishrobot]

When new line characters exist in an element value, there seems to be a
different unmarshalling behavior between the element is defined as primitive
type (xs:token) and as simpletype with enumeration under restriction (xs:token).

Environment

Operating System: All
Platform: All

Affected Versions

[2.2.4]

[glassfishrobot]

Reported by hongjoon@java.net

[glassfishrobot]

Was assigned to snajper

[glassfishrobot]

hongjoon@java.net said:
Created an attachment (id=286)
test schema file

[glassfishrobot]

File: test.xsd
Attached By: hongjoon@java.net

[glassfishrobot]

File: test.xml
Attached By: hongjoon@java.net

[glassfishrobot]

hongjoon@java.net said:
Created an attachment (id=287)
test xml document file

[glassfishrobot]

hongjoon@java.net said:
Created an attachment (id=288)
test java file

[glassfishrobot]

File: Test.java
Attached By: hongjoon@java.net

[glassfishrobot]

hongjoon@java.net said:
result is as follows:

elem1: elem1Value
elem2: \nelem2Value\n
elem3: null

I think elem3's value should be also 'elem3Value' like elem1's value.

The issue, 'https://jaxb.dev.java.net/issues/show_bug.cgi?id=592' was my faulty
test, sorry.

thanks.

[glassfishrobot]

@pavelbucek said:
simple workaround:

if you modify xml file like this

elem1Value elem2Value elemValue

you will get expected result. However I will look at this (firstly I have to
check specification, I don't know whether whitespace characters are allowed in
enums).

[glassfishrobot]

@pavelbucek said:
your issue is valid - whitespace characters in enums should be trimmed

fixed in trunk

[glassfishrobot]

hongjoon@java.net said:
Thank you very much for your fixing.
I think whitespace characters in enums should be trimmed only when its type is
restricted with "xs:token", not "xs:string".

Anyway, do you have any idea of applying the fixed version to 2.1 branch?

Thank you.

[glassfishrobot]

@pavelbucek said:
I've checked it - trimming is in place even if xs:string is used as restriction
base.

This fix will be included in JAXB 2.1.11 which will be released within six months.

[glassfishrobot]

snajper said:
Incorrect fix, regression, string values shall not be trimmed.

[glassfishrobot]

snajper said:
Fixed in trunk/2.2 branch.