Xerces gMonth issue

[Joe Qiu <Jo...@infosys.com>]

Dear Sir/Miss
                I got an exception saying that --01-- is not a valid value for gMonth in our production environment, current the JRE version is jre1.6 minor version 14.
                Could you please help me to check which later jre version fixed the issue?

Best regards,
Joe

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are not 
to copy, disclose, or distribute this e-mail or its contents to any other person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys has taken 
every reasonable precaution to minimize this risk, but is not liable for any damage 
you may sustain as a result of any virus in this e-mail. You should carry out your 
own virus checks before opening the e-mail or attachment. Infosys reserves the 
right to monitor and review the content of all messages sent to or from this e-mail 
address. Messages sent to or from this e-mail address may be stored on the 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

Re: Xerces gMonth issue

[Michael Glavassevich <mr...@ca.ibm.com>]

Hi Joe,

"--01--" is invalid, but Xerces has tolerated it for compatibility reasons
[1]. Apparently Oracle/Sun decided to stop supporting it. You would have to
ask them about it. We have no influence over what they do in their JDK/JRE
releases.

Thanks.

[1] http://xerces.apache.org/xerces2-j/xml-schema.html

Michael Glavassevich
XML Technologies and WAS Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org

Joe Qiu <Jo...@infosys.com> wrote on 11/03/2011 05:20:10 AM:

> Dear Sir/Miss
>                 I got an exception saying that --01-- is not a valid
> value for gMonth in our production environment, current the JRE
> version is jre1.6 minor version 14.
>                 Could you please help me to check which later jre
> version fixed the issue?
>
> Best regards,
> Joe