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

Jacob Danner commented on XMLBEANS-320:
---------------------------------------

Hmm, so I don't have the same system you do, (I'm on my XP machine) but this is 
passing for me:
</ManifestFile>
NODE Values (works) start=2007-04-01, end=2007-04-08
Duration start=2007-04-01, end=2007-04-01
NODE Values (works) start=2007-04-01, end=2007-04-08
Duration start=2007-04-01, end=2007-04-01

with a few adjustments as I don't have the IDTParser.
The changes I made are below
                File f=new 
File("D:\\svn\\xmlbeans\\trunk\\reproDir\\ContentOrder.xml");
                
                ManifestFileDocument mf = ManifestFileDocument.Factory.parse(f);
        ArrayList errors = new ArrayList();
        XmlOptions xo = new XmlOptions();
        xo.setErrorListener(errors);
        if( mf.validate(xo)){
            for (int i = 0; i < errors.size(); i++) {
                System.out.println("["+i+"]-"+(XmlError)errors.get(i));
            }
        }
                System.out.println(mf);
                
                OrderHeader[] headers = 
mf.getManifestFile().getDigitalContentOrders().getOrderHeaderArray();


> 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, 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to