One more

[system]

I saved a few, sorry to have send the previous errors in separate
messages before, it was not my purpose to make a lot of noise.

same archetype, lines containing :

time_attr6 matches {|00:00:59,0|}
date_time_attr2 matches {yyyy-mm-ddThh:mm:??; 1995-03-17T12:01}
date_time_attr3 matches {yyyy-mm-ddThh:mm:XX; 1995-03-17T12:01}
date_time_attr4 matches {yyyy-mm-ddThh:??:XX; 1995-03-17T12:01}
date_time_attr5 matches {yyyy-??-??T??:??:??; 1995-03-17T12:01}
date_time_attr6 matches {|1983-12-25T22:00:05,0|}
date_time_attr7 matches {|2000-01-01T00:00:59,0|}

I leave the stacktraces out, If needed I can reproduce them

So, they are all date-time related errors, the only one in this
test-archetype which is accepted is:
date_time_attr1 matches {yyyy-mm-ddThh:mm:ss; 1995-03-17T12:01:30}

regards
Bert

[system]

Bert

One problem I think is that the Parser doesn’t use the ISO8601 extended dates/times as it should per specification, but simpler Date/times.

Specs:

V_ISO8601_EXTENDED_DATE_TIME YYYY-MM-DDThh:mm:ss[,sss][Z|+/-

(attachments)

[system]

Hi Bert, Sebastian,

It does support ISO8601 extended dates/times. The issue is caused by the separator for millisecond. It should be “,” not “.” according to the ADL specs. It should be corrected.

Thanks!
/Rong

(attachments)