During XML-Java serialisation, if generated Java types (from XSD types) have any date field of javax.xml.datatype.XMLGregorianCalendar,
we noticed that after SmartClient construt JavaScript array from this data, the date format is coming as XML schema type.
And also, JavaScript object is coming where we have to extract day, month, year, hour, min, sec to construct string/text representation of require display date.
This is causing a code change in our UI layer which we don't prefer.
However, when java.util.Calendar is used for date property in Java types, the date is coming as text/string in JavaScript object which is
straightforward to display in UI without any further parsing logic.
Any specific reason for this behaviour or whether SmartClient supports JS serialisation of javax.xml.datatype.XMLGregorianCalendar type.
Java 8 JAXB is used to generate types from XSD types.
SmartClient 12.1-p20211102
we noticed that after SmartClient construt JavaScript array from this data, the date format is coming as XML schema type.
And also, JavaScript object is coming where we have to extract day, month, year, hour, min, sec to construct string/text representation of require display date.
This is causing a code change in our UI layer which we don't prefer.
However, when java.util.Calendar is used for date property in Java types, the date is coming as text/string in JavaScript object which is
straightforward to display in UI without any further parsing logic.
Any specific reason for this behaviour or whether SmartClient supports JS serialisation of javax.xml.datatype.XMLGregorianCalendar type.
Java 8 JAXB is used to generate types from XSD types.
SmartClient 12.1-p20211102
Comment