Hi all, latest push on master introduces engine lifecycle extensions as another JSPWiki extension point. It allows custom components (plugins, filters, etc.) to be aware of Engine's initialization and shutdown, without having to deep dive on Engine's internals.
Examples of EngineLifecycleExtension's use cases: * Appending a plugin's classpath to jspwiki.plugin.searchPath, so it can be used as a drop-in, without further configuration on the JSPWiki instance. * Setting up that expensive singleton, or disposing resources, without having to use or register a WikiEventListener. * Providing default parameters or setup for a custom extension. They don't provide too much value on themselves, but are perfect companions for custom plugins, filters, etc. As such, Engine lifecycle extensions are expected to be usually bundled with another custom component. As a concrete example, the markdown module uses an EngineLifecycleExtension to set up all the required properties if jspwiki.syntax=markdown is provided on the jspwiki[-custom].properties file. So, instead of providing jspwiki.renderingManager.markupParser=org.apache.wiki.parser.markdown.MarkdownParser jspwiki.renderingManager.renderer=org.apache.wiki.render.markdown.MarkdownRenderer jspwiki.renderingManager.renderer.wysiwyg=org.apache.wiki.render.markdown.MarkdownRenderer jspwiki.syntax.decorator=org.apache.wiki.htmltowiki.syntax.markdown.MarkdownSyntaxDecorator on the jspwiki[-custom].properties file, now the same can be accomplished by providing jspwiki.syntax=markdown which is not only less configuration, but much more expressive in terms of what we do want to achieve by setting that/those properties. The https://jspwiki-wiki.apache.org/Wiki.jsp?page=HowToWriteAnEngineLifecycleExtension page contains more details on how to code your own engine lifecycle extension. best regards, juan pablo
