[
https://issues.apache.org/jira/browse/CXF-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-1026.
------------------------------
Resolution: Invalid
Fix Version/s: Invalid
The command line parsing is handling this correctly and it does work for things
like the -packagename thing on wsdl2java. The problem for CXF-1027 is
slightly different. When populating the ToolContext, the parseArguements
method is passed a set of args that should call doc.getParameters insteadof
getParameter. The "bean" arg isn't in that set.
> multiple-occurence arguments don't seem to work in tooling argument processing
> ------------------------------------------------------------------------------
>
> Key: CXF-1026
> URL: https://issues.apache.org/jira/browse/CXF-1026
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Affects Versions: 2.0.1
> Reporter: Benson Margulies
> Assignee: Daniel Kulp
> Fix For: Invalid
>
>
> The command-line parsing system allows for multiple occurences of options in
> the xml spec for an option. For example:
> <option id="beans" maxOccurs="unbounded">
> <annotation>Specify the pathname of a file
> defining additional Spring beans to customize databinding
> configuration.</annotation>
> <switch>beans</switch>
> <associatedArgument placement="afterSpace">
> <annotation>pathname of the bean
> definition file.</annotation>
> </associatedArgument>
> </option>
> However, these don't seem to really work. By the time the code assembles the
> HashMap from options to values, any non-first occurences any option are
> discarded without diagnosis. It seems to me that, if maxOccurs != 1, that the
> value in the map should be a List<String>, accumulated from the occurences.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
