[
https://issues.apache.org/jira/browse/WW-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165572#comment-13165572
]
Ilya commented on WW-3720:
--------------------------
Probably not a really strong arguments, but:
* It is more easy to modify and process this XML programatically. Many IDEs
(like IDEA) support Struts config files: they parse it and may "link" action to
class (so "rename class", "find usage" and other tools work) and they may link
method too.
* Collection is better than String in method signature, more semantic and no
need to split it.
It is really minor issue but it has some benefits)
> Support collection-based properties in .xml
> -------------------------------------------
>
> Key: WW-3720
> URL: https://issues.apache.org/jira/browse/WW-3720
> Project: Struts 2
> Issue Type: New Feature
> Reporter: Ilya
> Priority: Minor
> Fix For: Future
>
>
> MethodFilterInterceptor.setExcludeMethods accepts coma-separated list of
> methods and it should be typed in such way in XML too.
> It would be much better to support collections:
> <param name="workflow.excludeMethods">
> <list>
> <element>input</element>
> <element>back</element>
> <element>cancel</element>
> </list>
> </param>
> and
> MethodFilterInterceptor.setExcludeMethods(String... methods)
> or
> MethodFilterInterceptor.setExcludeMethods(Collection<String> methods)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
