Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [xsd-dev] RE: Detecting errors in XSD Parsing


Yes, the validation support was already present in the 1.0.1 version, so
there should be no need to get the latest.

In general, you should always get a matching version of EMF (ecore.jar,
common.jar, etc) to go with the XSD version; they are always dropped at the
same time with matching build versions.  (Although it would probably work

Ed Merks/Toronto/IBM@IBMCA
mailto: merks@xxxxxxxxxx
905-413-3265  (t/l 969)

                      "Hayden Marchant"                                                                                                       
                      <Hayden.Marchant@u        To:       <xsd-dev@xxxxxxxxxxx>                                                               
            >               cc:                                                                                           
                      Sent by:                  Subject:  [xsd-dev] RE: Detecting errors in XSD Parsing                                       
                      03/11/2003 11:03                                                                                                        
                      Please respond to                                                                                                       

will this work on Eclipse XSD 1.0.1? or do I have to install XSD 1.0.2?

Are there any requirements to use more updated jars of eclipse with this
new 1.0.2 release or will it work with the old jars (ecore.jar, common.jar


-----Original Message-----
From: Ed Merks [mailto:merks@xxxxxxxxxx]
Sent: Tuesday, March 11, 2003 2:22 PM
To: Hayden Marchant
Subject: Re: Detecting errors in XSD Parsing


If you call  XSDConcreteComponent.validate on your XSDSchema, it will
the whole schema.  For this particular case, it will produce a diagnostic
indicating that gfgfd is not permitted.

Hayden Marchant wrote:

> I need to be able to detect bad xsd's during parsing. For example, if
> there is an XSD with a snippet like this:
>         <xsd:complexType name="stim">
>                 <xsd:sequence>
>                         <xsd:gfgfd name="This" type="xsd:string"/>
>                         <xsd:element name="that" type="xsd:string"/>
>                 </xsd:sequence>
>         </xsd:complexType>
> I would like the parser to notify me somehow that the first thing in the
> sequence is not a legal xsd construct. Instead it continues parsing with
> complex type and says it has just one element. I tried calling
> XSDSchema.getDiagnostics() but got an empty list. Does anyone know under
> what conditions getDiagnostics returns errors?
> Obviously there are a lot more things that can go wrong with parsing -
> anyone point me in the right direction?
> Thanks,
> Hayden Marchant

xsd-dev mailing list

Back to the top