[Announce] DDMSence 2.4.0 released
5 views
Skip to first unread message
Brian Uri!
Nov 20, 2014, 2:14:47 PM11/20/14
to ddms...@googlegroups.com
Hello everyone,
DDMSence v2.4.0 is now available for download. This is a stable, minor release which improves the handling of date attributes in various DDMS components. It is backwards compatible with all versions since v2.0.0. It should appear in the Maven Central Repository within the next few hours.
In the previous version of DDMSence, date values were translated differently depending on their data type. Dates in standard schema formats were automatically converted into XMLGregorianCalendar instances (exposed as accessors on each DDMSComponent), while dates in the custom DDMS format were not converted at all. Users had to grab the custom date as a raw string and do all of the conversion manually.
In v2.4.0, the custom DDMS format is treated in the same way as the standard schema formats. Any missing, optional fields (e.g. the seconds or milliseconds) are set to 0. This allows users to get an XMLGregorianCalendar instance automatically from the accessor method, regardless of the underlying data type. The table below shows how various date attribute values were converted in the v2.3.0 and v2.4.0. As you can see from the highlighted cells, only a particular subset of data is affected.
Thank you for your continued support!
BU
DDMSence v2.4.0 is now available for download. This is a stable, minor release which improves the handling of date attributes in various DDMS components. It is backwards compatible with all versions since v2.0.0. It should appear in the Maven Central Repository within the next few hours.
In the previous version of DDMSence, date values were translated differently depending on their data type. Dates in standard schema formats were automatically converted into XMLGregorianCalendar instances (exposed as accessors on each DDMSComponent), while dates in the custom DDMS format were not converted at all. Users had to grab the custom date as a raw string and do all of the conversion manually.
In v2.4.0, the custom DDMS format is treated in the same way as the standard schema formats. Any missing, optional fields (e.g. the seconds or milliseconds) are set to 0. This allows users to get an XMLGregorianCalendar instance automatically from the accessor method, regardless of the underlying data type. The table below shows how various date attribute values were converted in the v2.3.0 and v2.4.0. As you can see from the highlighted cells, only a particular subset of data is affected.
Thank you for your continued support!
BU
Reply all
Reply to author
Forward
0 new messages