[
https://issues.apache.org/jira/browse/AXIS2-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721250#action_12721250
]
Maite Clay commented on AXIS2-4099:
-----------------------------------
Ahh.. that is too bad for me then. I am stuck using that particular IBM jvm
for now, and is seems it the JVM that is broken in this scenario. No axis1.5
for me until the folks at work update the jvm. Hopefully IBM has fixed the bug.
I also tried it once I got home and it worked with the following JVMs.
java version "1.5.0_16"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b02)
Java HotSpot(TM) Client VM (build 1.5.0_16-b02, mixed mode, sharing)
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)
> ConverterUtil.convertToDateTime() is to lenient
> -----------------------------------------------
>
> Key: AXIS2-4099
> URL: https://issues.apache.org/jira/browse/AXIS2-4099
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: adb
> Affects Versions: 1.4.1, 1.4, 1.3
> Reporter: Marcel Ammerlaan
> Priority: Minor
> Attachments: DateTimeBug.java
>
>
> When parsing an invalid date (as specified by the XSD Schema specification),
> Axis relies on the java.util.Calendar leniency to parse. E.g. 2008-02-31
> (31st of februari) is invalid according to
> http://www.w3.org/TR/xmlschema-2/#dateTime. convertToDateTime() returns the
> 2nd of march instead.
> This can be easily solved by setting the Calender leniency to false
> (setLenient(false)).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
