Modello

Date formats supported by XML readers/writers are not consistent across plugins

Details

  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

XPP3 generated readers/writers consider a Date as a long
Dom4J generated readers/writers consider a Date as a Date formatted by DateFormat.getDateTimeInstance( DateFormat.FULL, DateFormat.FULL , Locale.US )

an XML document with a Date generated by XPP3 writer can't be read by a reader generated by Dom4j...

Issue Links

depends upon

Bug - A problem which impairs or prevents the functions of the product. MODELLO-127 Dom4j plugin should support xml.format attribute

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is related to

Improvement - An improvement or enhancement to an existing feature or task. MODELLO-178 add xml.format="long" option to read/write a date field as a long value

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Herve Boutemy added a comment -

problem shown in r953

Show
Herve Boutemy added a comment - problem shown in r953
Hide
Permalink
Herve Boutemy added a comment -

working on this issue, I found that xml.format field attribute exists to define a DateFormat in XML documents: then having different default Date format is not really a severe problem.

Now, every XML plugins should support this xml.format attribute, which is not the case (see MODELLO-127).
But that's another story...

Show
Herve Boutemy added a comment - working on this issue, I found that xml.format field attribute exists to define a DateFormat in XML documents: then having different default Date format is not really a severe problem. Now, every XML plugins should support this xml.format attribute, which is not the case (see MODELLO-127 ). But that's another story...
Hide
Permalink
Herve Boutemy added a comment -

done in r1136
default date format is now yyyy-MM-dd'T'HH:mm:ss.SSS, which is the more accurate date format compatible with XML Schema

Show
Herve Boutemy added a comment - done in r1136 default date format is now yyyy-MM-dd'T'HH:mm:ss.SSS , which is the more accurate date format compatible with XML Schema
Hide
Permalink
Igor Fedorenko added a comment -

This seems to introduce compatibility problems. I need to be able to read/write the same version of the model using code generated by different versions of modello. Unless I am missing something, it is not possible to define model in such a way that it would to read/written correctly by the code generated before and after this change (i.e. SimpleDateFormat does not have format string to render date as long).

Show
Igor Fedorenko added a comment - This seems to introduce compatibility problems. I need to be able to read/write the same version of the model using code generated by different versions of modello. Unless I am missing something, it is not possible to define model in such a way that it would to read/written correctly by the code generated before and after this change (i.e. SimpleDateFormat does not have format string to render date as long).
Hide
Permalink
Herve Boutemy added a comment -
  • default format for Dom4J plugin is DateFormat.FULL and previously it didn't support xml.format attribute (see MODELLO-127)
  • but XPP3 format does support xml.format attribute

can't you set xml.format to the Dom4J format (have to retrieve the SimpleDateFormat equivalent value...)?

Show
Herve Boutemy added a comment - default format for Dom4J plugin is DateFormat.FULL and previously it didn't support xml.format attribute (see MODELLO-127 ) but XPP3 format does support xml.format attribute can't you set xml.format to the Dom4J format (have to retrieve the SimpleDateFormat equivalent value...)?
Hide
Permalink
Igor Fedorenko added a comment -

I work with a project (nexus) that is currently using modello 1.0-alpha-2x. xpp3 io code generated with that modello version uses Date.getTime() I belive. If I upgrade Nexus to modello 1.0, the new code will use "yyyy-MM-dd'T'HH:mm:ss.SSS" by default. What is worth, though, I cannot force the old date format and have to bump model version. Which unfortunately means the old code will not be able to read/write the model any more.

Show
Igor Fedorenko added a comment - I work with a project (nexus) that is currently using modello 1.0-alpha-2x. xpp3 io code generated with that modello version uses Date.getTime() I belive. If I upgrade Nexus to modello 1.0, the new code will use "yyyy-MM-dd'T'HH:mm:ss.SSS" by default. What is worth, though, I cannot force the old date format and have to bump model version. Which unfortunately means the old code will not be able to read/write the model any more.
Hide
Permalink
Herve Boutemy added a comment -

ok, I think I understand

proposal: if xml.format="long", generated code won't use SimpleDateFormat but a long value (like it was done before for XPP3)

would it be ok for you?

Show
Herve Boutemy added a comment - ok, I think I understand proposal: if xml.format="long" , generated code won't use SimpleDateFormat but a long value (like it was done before for XPP3) would it be ok for you?
Hide
Permalink
Igor Fedorenko added a comment -

yes, I think this should work.

Show
Igor Fedorenko added a comment - yes, I think this should work.
Hide
Permalink
Herve Boutemy added a comment -

created MODELLO-178 issue to track this xml.format="long" improvement

Show
Herve Boutemy added a comment - created MODELLO-178 issue to track this xml.format="long" improvement

People

  • Assignee:
    Herve Boutemy
    Reporter:
    Herve Boutemy
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: