Support of gYearMonth, gYear, gMonthDay, gMonth, gDay types.

[duschata]

Hello All,
I've tried to compile a XSD Schema including xsd:gYear(...) to a mapping file. Marshalling and unmarshalling fails. Take a look at the attached index.html. I've tried to fix it (also available in the .zip), its not implemented yet (Snapshot 2.1.5). Have you planned to implement the support for gYear...?.
Kind Regards
Thomas Grabietz
file: https://mega.co.nz/#!ylkhXKgS!WhHt0OQSCSA91DvxB9BHVl2wx4g8G7DoKhZNcHK8N_Q

[highsource]

I can't access your attachment, sorry. Please send me the mail to valikov(-)gmx.net.

Actually gYear, gMonth and so on should be supported already, see here.

[highsource]

Or even better please make a JSFiddle (see this example).

[highsource]

See also:
http://jira.highsource.org/browse/JSNX-3

[highsource]

See also:
https://code.google.com/p/jsdatatypelibrary/source/browse/trunk/jsdatatypelibrary/datatype_library.js

[highsource]

Reproduced.

The status is: g* types are really not supported yet.

• Jsonix.Schema.XSD.Calendar should be extended to support gYearMonth, gYear, gMonthDay, gMonth, gDay types.
• Jsonix.Schema.XSD.G* types extend Jsonix.Schema.XSD.Calendar and call the appropriate parse/print methods.

[highsource]

Implementation hints:

• Calendar should detect the pattern here. The best would be probably with a regexp. These are good hints, but I won't use the code directly because I'm not sure those expressions are correct and also because of the license. Better to write regular expressions from scratch based on the spec 3.2.10 - 3.2.14.
• Add parseGYearMonth ... parseGDay methods called when a certain regexp is detected in parse
• The reverse in print: check what the object contains, call the printGYearMonth...printGDay accordingly, throw an error if the combination does not match any type.
• In GYearMonth ... GDay, extend the Calendar and call the appropriate print/parse methods. Validate the input both on print and parse.
• Tests go here, will probably make sense splitting in smaller test methods. To build, you'll need to mvn clean install scripts and then mvn clean install in nodejs/scripts and then you should be able to npm test. This is awkward at the moment.
• Issue-speicific test is here, at the moment commented out
• Relevant XJC plugin class is here, basically you'll have to comment out the mappings.
• This is more or less it. Probably a few tests will fail or will have to be extended, but that's minor.