You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Aaron Kaplan (JIRA)" <ui...@incubator.apache.org> on 2007/11/07 13:17:50 UTC
[jira] Created: (UIMA-619) Wrong error message when loading type
system
Wrong error message when loading type system
--------------------------------------------
Key: UIMA-619
URL: https://issues.apache.org/jira/browse/UIMA-619
Project: UIMA
Issue Type: Bug
Components: Core Java Framework
Affects Versions: 2.2
Reporter: Aaron Kaplan
Priority: Minor
If I try to load the following type system definition
<typeSystemDescription xmlns="http://uima.apache.org/resourceSpecifier">
<name>InfomagicTypeSystem</name>
<types>
<typeDescription>
<name>Foo</name>
<supertypeName>Bar</supertypeName>
</typeDescription>
<typeDescription>
<name>Bar</name>
<supertypeName>Baz</supertypeName>
</typeDescription>
</types>
</typeSystemDescription>
I get the error message 'Undefined type "Bar", referenced as supertype of type "Foo"'. This is misleading, because Bar *is* defined. The real problem is that Baz is undefined.
This is order-dependent: if I define Bar before Foo, then I get the appropriate message about Baz being undefined.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-619) Wrong error message when loading type
system
Posted by "Thilo Goetz (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thilo Goetz closed UIMA-619.
----------------------------
Resolution: Fixed
Fix Version/s: 2.3
Thanks for reporting this.
> Wrong error message when loading type system
> --------------------------------------------
>
> Key: UIMA-619
> URL: https://issues.apache.org/jira/browse/UIMA-619
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Affects Versions: 2.2
> Reporter: Aaron Kaplan
> Assignee: Thilo Goetz
> Priority: Minor
> Fix For: 2.3
>
>
> If I try to load the following type system definition
> <typeSystemDescription xmlns="http://uima.apache.org/resourceSpecifier">
> <name>InfomagicTypeSystem</name>
> <types>
> <typeDescription>
> <name>Foo</name>
> <supertypeName>Bar</supertypeName>
> </typeDescription>
> <typeDescription>
> <name>Bar</name>
> <supertypeName>Baz</supertypeName>
> </typeDescription>
> </types>
> </typeSystemDescription>
> I get the error message 'Undefined type "Bar", referenced as supertype of type "Foo"'. This is misleading, because Bar *is* defined. The real problem is that Baz is undefined.
> This is order-dependent: if I define Bar before Foo, then I get the appropriate message about Baz being undefined.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-619) Wrong error message when loading type
system
Posted by "Thilo Goetz (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thilo Goetz reassigned UIMA-619:
--------------------------------
Assignee: Thilo Goetz
> Wrong error message when loading type system
> --------------------------------------------
>
> Key: UIMA-619
> URL: https://issues.apache.org/jira/browse/UIMA-619
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Affects Versions: 2.2
> Reporter: Aaron Kaplan
> Assignee: Thilo Goetz
> Priority: Minor
>
> If I try to load the following type system definition
> <typeSystemDescription xmlns="http://uima.apache.org/resourceSpecifier">
> <name>InfomagicTypeSystem</name>
> <types>
> <typeDescription>
> <name>Foo</name>
> <supertypeName>Bar</supertypeName>
> </typeDescription>
> <typeDescription>
> <name>Bar</name>
> <supertypeName>Baz</supertypeName>
> </typeDescription>
> </types>
> </typeSystemDescription>
> I get the error message 'Undefined type "Bar", referenced as supertype of type "Foo"'. This is misleading, because Bar *is* defined. The real problem is that Baz is undefined.
> This is order-dependent: if I define Bar before Foo, then I get the appropriate message about Baz being undefined.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.