[
https://issues.apache.org/jira/browse/JSPWIKI-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646453#action_12646453
]
Andrew Jaquith commented on JSPWIKI-423:
----------------------------------------
A few quick thoughts:
* It's true, Stripes 1.5 does not scan the entire classpath anymore... and this
is definitely a feature because it speeds up startup
* The Stripes approach for locating optional classes is to specify what
packages contain Stripes "extensions". This is done by having ResolveUtil
search a comma-separated list of packages in a servlet init-param, e.g.,
"com.ecyrd.jspwiki.action,net.sf.stripes".
* JSPWiki could do the same thing (but configure the packages to search via
jspwiki.proprties, I'd expect)
Also, could we think a little more creatively about the annotation name?
"ModuleData" just leaves me cold. I'd suggest something a little more
suggestive of the classes it annotates. For example, "WikiExtension" or
"WikiModule" is a lot better.
> Plugins should use annotations instead of jspwiki_module.xml
> ------------------------------------------------------------
>
> Key: JSPWIKI-423
> URL: https://issues.apache.org/jira/browse/JSPWIKI-423
> Project: JSPWiki
> Issue Type: Improvement
> Components: Plugins
> Reporter: Janne Jalkanen
> Assignee: Janne Jalkanen
> Fix For: 3.0
>
>
> Use of annotations makes it much easier to keep a plugin up to date. Please
> see org.apache.jspwiki.api.ModuleData annotation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
