-
New Feature
-
Resolution: Fixed
-
Major
-
2.0.0 M3
-
None
Current XML schema for plugin.xml can not be extended.
Indeed, internal configuration of components or extensions can not come with their schema and therefore do not benefit from validation or completion.
I propose to:
- change processContents of extension and component element from "skip" to "lax"
- search for files META-INF/runtime-schema in classpath for registering new schema (http://www.ametys.org/schema/*)
- use the namespace http://www.ametys.org/schema/plugin for elements in plugin.xml
[RUNTIME-268] Add possibility to extend plugin.xsd in order to benefit from validation and completion
Sébastien Launay (Inactive)
added a comment - Added in revisions 630 to 632.
Double logged exceptions in PluginsManager have been removed.
Sébastien Launay (Inactive)
added a comment - Added in revisions 630 to 632.
Double logged exceptions in PluginsManager have been removed. 
Added local schemas support in revision 664.
Any plugin can now declares new schemas by putting one or more .xsd files into its plugin directory.
The convention is to compute the schema location by concatenating http://www.ametys.org/schema/ with the file name.
Therefore, if there is a file web/plugins/myplugin/my-plugin-1.0.xsd then this schema is registered for location http://www.ametys.org/schema/my-plugin-1.0.xsd.
The schema namespace is generally http://www.ametys.org/schema/my-plugin but this is not mandatory.
Note that local schema override embedded schema (for the same schema location).