Community
Participate
Working Groups
When working with an exsd file, an error is only shown within the Extension Point Schema editor, whereas it should also result in an entry in the Problems view and decorators (on the file, parent folder(s), project and working set(s)) in the Package Explorer view. Only showing the problem in the editor means that you only see the error when the editor is open and you're paying particular attention to the editor's details.
Created attachment 87223 [details] Screen shots
Sounds logical. Attaching a schema to test with. I modified PDE schema to provide an unresolved "included schema" and an unresolved element in a sequence which should provide similar results as to what Simon is experiencing.
Created attachment 87224 [details] test schema definition example schema definition
Created attachment 142797 [details] Patch for SchemaErrorReporter.java I've added additional validation steps to SchemaErrorReporter. It now validates if included schemas are valid and also if referenced elements are defined. Errors are reported in problems view and package explorer.
Thanks Simon!
If this is good, we can commit this towards M1.
Thanks for this simple and elegant patch Simon :-) I've released it with minor wording changes for the error messages. It is available in HEAD > 20090728. Since we now handle included schemas, I've opened bug 215743 in order to improve the schema compiler to trigger recompilation of every depending schema(s) on a schema modification...