Announcement Announcement Module
Collapse
No announcement yet.
Improved consistency in component type configuration Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Improved consistency in component type configuration

    FYI...

    I've made some additions to how component types/component are configured (whilst retaining backwards compatibility of the old style).

    All component types WebScript, Freemarker and JSP can now use the <uri> element. Previously, JSPs URIs were specified using the <jsp-path> element (and this is still supported) and all examples for WebScripts only showed the URI configured via the <url> element in the component.

    Although no code has changed for the WebScript processing it's worth noting that by providing a <uri> element in the component type configuration you don't need to specify a URL for every component instance (although you can still do this to override the component type value for a specific instance).

    It also means that you can provide different URIs for each render mode ("view", "edit", "admin" and "help") which is not possible when relying on component overrides.

    There are still inconsistencies that could be addressed going forward (the use of <uri> in component types vs <url> in component overrides) but hopefully this should make switching between processing engines more straight forward.
Working...
X