After schema validating an XML instance loaded from disk I would like
to perform some extra programmatic validations not covered by the XML
schema. For the extra validation I hope to re-use xmlbeans XmlError
and XmlException. However if I create an XmlError using:
Wing Yew,
Thanks for the response. I have no idea what version of XMLBeans we *were*
usingI downloaded it and built our schema jar in March of 2006. We did not
find this error until we started attempting to export data earlier this year.
And yes, the version I'm using now is built from the
Intermittent errors usually lead me to suspect a threading issue --
either in your code or XmlBeans. Is the marshaling in your code being
handled in another thread? Or perhaps there are multiple threads doing
the export work from the database?
Can anyone on the list assert how thread-safe the
Tim,
Thanks for the reply. This schema is a national standard for the submission of
Emergency Medical Services incident data, and has been in the public for 5
years. I can't change the schema. The database column SHOULD have been a
string, and since it isn't, is going to cause some major
The compilation errors below are also a huge problem, because I cannot
regenerate my schema jar.
From: Paul Cooper [mailto:pcoo...@emspic.org]
Sent: Thursday, September 23, 2010 6:59 PM
To: user@xmlbeans.apache.org
Subject: Error compiling schema
Greetings, list. Longtime user of older versions
Paul,
since it appears that your former co-worker was thinking of a different bug
than the truncation problem you're seeing, there is no gain for you to live on
the bleeding edge of XMLBeans. Why don't you try using the released XMLBeans
2.5.0 and recompile your schema? Let us know if
Hmmm. I hadn't thought of that. I'll try it and see what happens! Thanks.
Forest and trees and stuff.
From: Wing Yew Poon [mailto:wing.yew.p...@oracle.com]
Sent: Friday, September 24, 2010 11:10 AM
To: user@xmlbeans.apache.org
Subject: RE: Error compiling schema
Paul,
since it appears that
7 matches
Mail list logo
