JDK-2193403 : XML Duration do not conform to W3C specifications
  • Type: Backport
  • Backport of: JDK-6937964
  • Component: xml
  • Sub-Component: jaxp
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2010-05-19
  • Updated: 2012-06-08
  • Resolved: 2010-07-01
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other JDK 6
1.4.0 1.4Fixed 6u20-revFixed
Comments
EVALUATION Fix TCK failures. The method signatures for newDuration and newDurationDayTime are inconsistent in regards to the seconds parameter, the former uses BigDecimal but the later BigInteger. The corresponding DurationImpl constructor does take a BigDecimal seconds. However, since newDurationDayTime was not implemented in DataTypeFactoryImpl, the problem did not manifest itself before. Used the same approache as the API impl; Added tests from the TCK.
19-05-2010

EVALUATION Implementing yearMonthDuration and dayTimeDuration. The Java API document for DatatypeFactory defined newDurationYearMonth and newDurationDayTime in accordance with XQuery 1.0 and XPath 2.0 Data Model, even though the later was not completed when jaxp 1.4 was finalized. The current implementation merely constructed a generic Duration when these methods are called. Note that unit tests such as DatatypeFactoryTest may contain test cases that do not follow the specification and may fail due to these changes. Some followup works may be needed on either test cases or the implementation.
19-05-2010