After resolving CMS-8304, the protocol view is now searching in the defined or current plugin before searching into the CMS plugin.

Behavior of the view protocol, search the file into the following locations :

1. current skin (*)
2. plugin WEB (*)
3. WEB-INF/param/view folder
4. plugin defined in view:[pluginName]:// or if empty the current plugin
5. plugin CMS

(*) If the plugin WEB exists and the WebViewSelector is selected in runtime.xml

I am not convinced about the relevance of this improvement for several reasons :

1. The plugin is mandatory for skins (no ?)
2. If you want to call an XSL file from a specific, just call it
3. The defined or current plugin is red after the plugin WEB, then it always wins
4. In a specific plugin, there is now no way to get the XSL file from WEB if the plugin exists, then CMS.

Note : The whole content types from plugin ODF are not displayable without a skin (then the plugin WEB) for now.