[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xmlbeans-dev
Subject:    [jira] Commented: (XMLBEANS-320) compiled schema Unable to parse
From:       "Anand Sathe (JIRA)" <xmlbeans-dev () xml ! apache ! org>
Date:       2007-04-30 13:53:15
Message-ID: 31169289.1177941195564.JavaMail.jira () brutus
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/XMLBEANS-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492669 \
] 

Anand Sathe commented on XMLBEANS-320:
--------------------------------------

Having come across a similar issue with my code, I found that when I created a \
Calendar c = new GregorianCalendar(2007, 3, 1) for an xs:dateTime field, the \
generated XML was invalid - only the date component was written. I then created a \
Calender c = new GregorianCalendar(2007, 3, 1, 0, 0, 0) and the generated XML was now \
valid. Although this is most likely a shortcoming with the GregorianCalendar \
implementation, I would think that xmlbeans should enforce the time component, given \
that the dateTime field expects a Calendar...

> compiled schema Unable to parse xs:date field
> ---------------------------------------------
> 
> Key: XMLBEANS-320
> URL: https://issues.apache.org/jira/browse/XMLBEANS-320
> Project: XMLBeans
> Issue Type: Bug
> Components: XmlObject
> Affects Versions: Version 2.2
> Environment: Linux-Debian/Ubuntu 6.10/X86_64
> Reporter: Andy Brook
> Attachments: ContentOrder.xml, DateParseTest.java, DateParseTest.java, \
> ManifestFile1.xsd 
> 
> I have a provided schema that contains a Duration, comprising of start and end \
> xs:date fields.  The schema compiled perfectly and Im pulling out all data.  The \
> only problem is xs:date fields.  As soon as I access getStart (xs:date) I get the \
> following stack: Exception in thread "main" \
> org.apache.xmlbeans.impl.values.XmlValueOutOfRangeException: Invalid date value: \
> wrong type: 2007-04-01  at \
> org.apache.xmlbeans.impl.values.XmlObjectBase$ValueOutOfRangeValidationContext.invalid(XmlObjectBase.java:285)
>   at org.apache.xmlbeans.impl.values.JavaGDateHolderEx.lex(JavaGDateHolderEx.java:81)
>   at org.apache.xmlbeans.impl.values.JavaGDateHolderEx.set_text(JavaGDateHolderEx.java:56)
>   at org.apache.xmlbeans.impl.values.XmlObjectBase.update_from_wscanon_text(XmlObjectBase.java:1135)
>   at org.apache.xmlbeans.impl.values.XmlObjectBase.check_dated(XmlObjectBase.java:1274)
>   at org.apache.xmlbeans.impl.values.JavaGDateHolderEx.calendarValue(JavaGDateHolderEx.java:192)
>   at org.apache.xmlbeans.impl.values.XmlObjectBase.getCalendarValue(XmlObjectBase.java:1516)
>   at com.bvi.schemas.itds.interfaces.manifestFile.impl.DurationImpl.getStart(DurationImpl.java:42)
>  Given the only code I've actually written is the test code, and that I cannot \
> change the schema.  The xml document is valid according to the schema, and the \
> actual date node text appears to be ISO8601 (YYYY-MM-DD).  Is this a bug or am I \
> missing something? A workaround is to access the node directly, and get the child \
> node values out.  Schema, example XML and test code to be attached.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]