Try using v2 or the online tools; last
time I checked line numbers for errors were working.
http://xmlbeans.webappshosting.com/schemaToolsV103/Welcome.do
Cezar
From: P. Michael
Hutchins [mailto:pmh0232@xxxxxxxxxx]
Sent: Monday, January 10, 2005
2:31 PM
To: user@xxxxxxxxxxxxxxxxxxx
Subject: RE: XSD Validates in
xmlSpy, but Fails in scomp
Thank you, Yana.
The problem is:
- The XSD is long (there's something like 79
occurrences of ..Includes)
- I didn't write it; am just trying to use it.
- I'm even having immense trouble getting access to
anyone who's in charge of it.
- W/o decent error msgs, it's impractical to try to
find the offending lines.
..but your pointer does help at least a little.
Thaniks again,
-- M.
At 03:24 PM 1/10/2005, you wrote:
Well, I am sure there is someone who can answer this better, but what
is
the problem? I am looking at your error messages and it seems to me that
they are consistent with the XML Schema spec:
(e.g. see the part where it says " Schema Component Constraint:
minInclusive valid restriction
It is an *error* if any of the following conditions is true:")
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#cvc-mi
nInclusive-valid
And yes, the developers do monitor this list...but turnaround speed
varies...
Hope this helps/answers your question some. I have no insight as to why
it works with XmlSpy, I suspect XmlBeans adheres to the spec better?
-Yana
-----Original Message-----
From: Michael Engelhart [mailto:mengelhart@xxxxxxxxxx]
Sent: Monday, January 10, 2005 11:52 AM
To: user@xxxxxxxxxxxxxxxxxxx
Cc: Alex Kahn; Moshe Shapiro
Subject: Re: XSD Validates in xmlSpy, but Fails in scomp
I ran into this with a web service I was using a few months ago. As
I
don't have access to XmlSpy (I know the service provider validates with
it though) I couldn't verify what the problems with it were and the
service suggested I use something other then XmlBeans :-).
Anyway, just wanted to chime in to say that this error showed up in my
coding. I had to modify the xsd (i didn't use the offending
element
in my case so it didn't really matter) to get around it but that's not
the solution I would like for the long term.
Mike
On Jan 10, 2005, at 1:46 PM, P. Michael Hutchins wrote:
> offending XSD attached
>
> scomp does:
>
>>> scomp -src src -out CRD.jar CRDXMLSchema.xsd
>>> java -classpath ;C:\xmlbeans-1.0.3\lib\xbean.jar.
>> org.apache.xmlbeans.impl.tool.SchemaCompiler -src src -out CRD.jar
>> CRDXMLSchema.xsd
>> \CRDXMLSchema.xsd:0: error: Must be less than or equal to previous
>> maxInclusive
>> \CRDXMLSchema.xsd:0: error: Must be greater than or equal to previous
>> minInclusive
>> \CRDXMLSchema.xsd:0: error: Must be greater than or equal to previous
>> minInclusive
>> \CRDXMLSchema.xsd:0: error: Must be less than or equal to previous
>> maxInclusive
>> \CRDXMLSchema.xsd:0: error: Must be greater than or equal to previous
>> minInclusive
>> \CRDXMLSchema.xsd:0: error: Must be less than or equal to previous
>> maxInclusive
>> \CRDXMLSchema.xsd:0: error: Must be greater than or equal to previous
>> minInclusive
>> \CRDXMLSchema.xsd:0: error: Must be less than or equal to previous
>> maxInclusive
>> \CRDXMLSchema.xsd:0: error: Must be less than or equal to previous
>> maxInclusive
>> \CRDXMLSchema.xsd:0: error: Must be greater than or equal to previous
>> minInclusive
>> \CRDXMLSchema.xsd:0: error: Must be less than or equal to previous
>> maxInclusive
>> \CRDXMLSchema.xsd:0: error: Must be greater than or equal to previous
>> minInclusive
>> \CRDXMLSchema.xsd:0: error: Must be less than or equal to previous
>> maxInclusive
>> \CRDXMLSchema.xsd:0: error: Must be less than or equal to previous
>> maxInclusive
>> Time to build schema type system: 2.406 seconds
>> BUILD FAILED
>
> This seems to me to suggest there's a problem.
>
> I'm not familiar with all the ins & outs of xxxInclusive in an XSD..
> ..does anyone know whether this error even makes any sense..
> ..and, if so, what kind of construct would cause it
> (obv'ly, one would think that something in the XSD must be
> referencing/extending a previously-established allowable range...)
>
> (In an earlier email, I asked about the possibility of getting more
> info
> output w/ scomp error msgs. Two nice people replied - but
neither
> sounded
> like a developer; do the developers monitor this list? Is there an
> actually pactivcal way of getting such info?)
>
>
> Thanks,
>
> -- M.
>
<CRDXMLSchema.xsd>-----------------------------------------------------
> ----------------
> To unsubscribe, e-mail: user-unsubscribe@xxxxxxxxxxxxxxxxxxx
> For additional commands, e-mail: user-help@xxxxxxxxxxxxxxxxxxx
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@xxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: user-help@xxxxxxxxxxxxxxxxxxx
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@xxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: user-help@xxxxxxxxxxxxxxxxxxx
