Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc) » Error validating with ecore.xsd
Error validating with ecore.xsd [message #64177] |
Sat, 09 December 2006 23:54  |
Eclipse User |
|
|
|
I get the following validation error in ecore.xsd in 13 places.
"src-simple-type.2.b: A <restriction> element was found that has neither
a base [attribute] nor a <simpleType> element among its [children]. One
is required."
The lines are 352, 358, 361, 370, 373, 376, 379, 394, 397, 406, 409,
412, and 428.
The lines in question typically look like this:
<xsd:simpleType ecore:instanceClass="char" name="EChar">
<xsd:restriction/>
</xsd:simpleType>
It would appear that the empty <xsd:restriction/> is causing the pain,
but simply taking it out doesn't help.
Brian
|
|
|
Re: Error validating with ecore.xsd [message #64200 is a reply to message #64177] |
Sun, 10 December 2006 07:25   |
Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Brian,
Yes, the XSD model isn't properly flagging these errors causing me to
over look them. Likely I'll just have all these types restrict
xsd:string (since they can't restrict anySimpleType outside of the
schema for schemas). So we should really fix both the XSD model's not
diagnosing the problem as well as fix the EcoreSchemaBuilder to not
generate results with such errors in them and then use that to
regenerate Ecore.xsd. Please open a bugzilla and we'll address all
these issues.
Brian Vetter wrote:
> I get the following validation error in ecore.xsd in 13 places.
>
> "src-simple-type.2.b: A <restriction> element was found that has
> neither a base [attribute] nor a <simpleType> element among its
> [children]. One is required."
>
> The lines are 352, 358, 361, 370, 373, 376, 379, 394, 397, 406, 409,
> 412, and 428.
>
> The lines in question typically look like this:
>
> <xsd:simpleType ecore:instanceClass="char" name="EChar">
> <xsd:restriction/>
> </xsd:simpleType>
>
> It would appear that the empty <xsd:restriction/> is causing the pain,
> but simply taking it out doesn't help.
>
> Brian
|
|
|
Re: Error validating with ecore.xsd [message #64268 is a reply to message #64200] |
Mon, 11 December 2006 11:18  |
Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Brian,
I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=167445 and
committed the fixes for both 2.2.2 and 2.3.0.
Ed Merks wrote:
> Brian,
>
> Yes, the XSD model isn't properly flagging these errors causing me to
> over look them. Likely I'll just have all these types restrict
> xsd:string (since they can't restrict anySimpleType outside of the
> schema for schemas). So we should really fix both the XSD model's not
> diagnosing the problem as well as fix the EcoreSchemaBuilder to not
> generate results with such errors in them and then use that to
> regenerate Ecore.xsd. Please open a bugzilla and we'll address all
> these issues.
>
>
> Brian Vetter wrote:
>> I get the following validation error in ecore.xsd in 13 places.
>>
>> "src-simple-type.2.b: A <restriction> element was found that has
>> neither a base [attribute] nor a <simpleType> element among its
>> [children]. One is required."
>>
>> The lines are 352, 358, 361, 370, 373, 376, 379, 394, 397, 406, 409,
>> 412, and 428.
>>
>> The lines in question typically look like this:
>>
>> <xsd:simpleType ecore:instanceClass="char" name="EChar">
>> <xsd:restriction/>
>> </xsd:simpleType>
>>
>> It would appear that the empty <xsd:restriction/> is causing the
>> pain, but simply taking it out doesn't help.
>>
>> Brian
|
|
|
Re: Error validating with ecore.xsd [message #596740 is a reply to message #64177] |
Sun, 10 December 2006 07:25  |
Eclipse User |
|
|
|
Brian,
Yes, the XSD model isn't properly flagging these errors causing me to
over look them. Likely I'll just have all these types restrict
xsd:string (since they can't restrict anySimpleType outside of the
schema for schemas). So we should really fix both the XSD model's not
diagnosing the problem as well as fix the EcoreSchemaBuilder to not
generate results with such errors in them and then use that to
regenerate Ecore.xsd. Please open a bugzilla and we'll address all
these issues.
Brian Vetter wrote:
> I get the following validation error in ecore.xsd in 13 places.
>
> "src-simple-type.2.b: A <restriction> element was found that has
> neither a base [attribute] nor a <simpleType> element among its
> [children]. One is required."
>
> The lines are 352, 358, 361, 370, 373, 376, 379, 394, 397, 406, 409,
> 412, and 428.
>
> The lines in question typically look like this:
>
> <xsd:simpleType ecore:instanceClass="char" name="EChar">
> <xsd:restriction/>
> </xsd:simpleType>
>
> It would appear that the empty <xsd:restriction/> is causing the pain,
> but simply taking it out doesn't help.
>
> Brian
|
|
|
Re: Error validating with ecore.xsd [message #596762 is a reply to message #64200] |
Mon, 11 December 2006 11:18  |
Eclipse User |
|
|
|
Brian,
I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=167445 and
committed the fixes for both 2.2.2 and 2.3.0.
Ed Merks wrote:
> Brian,
>
> Yes, the XSD model isn't properly flagging these errors causing me to
> over look them. Likely I'll just have all these types restrict
> xsd:string (since they can't restrict anySimpleType outside of the
> schema for schemas). So we should really fix both the XSD model's not
> diagnosing the problem as well as fix the EcoreSchemaBuilder to not
> generate results with such errors in them and then use that to
> regenerate Ecore.xsd. Please open a bugzilla and we'll address all
> these issues.
>
>
> Brian Vetter wrote:
>> I get the following validation error in ecore.xsd in 13 places.
>>
>> "src-simple-type.2.b: A <restriction> element was found that has
>> neither a base [attribute] nor a <simpleType> element among its
>> [children]. One is required."
>>
>> The lines are 352, 358, 361, 370, 373, 376, 379, 394, 397, 406, 409,
>> 412, and 428.
>>
>> The lines in question typically look like this:
>>
>> <xsd:simpleType ecore:instanceClass="char" name="EChar">
>> <xsd:restriction/>
>> </xsd:simpleType>
>>
>> It would appear that the empty <xsd:restriction/> is causing the
>> pain, but simply taking it out doesn't help.
>>
>> Brian
|
|
|
Goto Forum:
Current Time: Sun May 11 15:20:55 EDT 2025
Powered by FUDForum. Page generated in 0.02965 seconds
|