[ 
https://issues.apache.org/jira/browse/CXF-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611391#action_12611391
 ] 

Dave Leatherdale commented on CXF-1692:
---------------------------------------

Absolutely agree that extraargs can still be useful. This set should probably 
only include the most important ones (although doing most of them while i was 
in the area was fairly easy hence it's a reasonably complete set).

It's a shame maven doesn't seem to document the parameters of these classes the 
same way it does the mojo parameters themselves.

A lot of the command line options have long options as well as short ones 
(although not all when i had a look) so we may be able to use those names 
(perhaps adding some more along the way) . We could use mavens Map parameter 
support to supply a lot of the command line parameters so 
<extraarg>-fe</extraarg><extraarg>jaxws</extraarg> could still be written as 
<frontend>jaxws</frontend> it wouldn't be able to cope with everything. For 
instance would be fairly easy to cope with either parameters with no arguments 
(e.g. -validate) OR with parameters with potentially empty parameters (e.g. 
-wsdlLocation "") but not both without some metadata on what "style" each 
parameter is at which point we come back to having to maintaining that. Also 
not sure if we can do lists of things in map parameters.



> cfx-codegen-plugin: Should be possible to configure using named parameters.
> ---------------------------------------------------------------------------
>
>                 Key: CXF-1692
>                 URL: https://issues.apache.org/jira/browse/CXF-1692
>             Project: CXF
>          Issue Type: Improvement
>          Components: Tooling
>    Affects Versions: 2.1.1
>            Reporter: Dave Leatherdale
>         Attachments: 1692.diff
>
>
> It should not be necessary to use extraargs to configure parameters named 
> parameter should be used instead. Extraargs should remain for unusual 
> circumstances and backwards compatibility.
> The options are configured as follows:
>                                       <defaultOptions>
>                                               <packagenames>
>                                                       
> <packagename>packagename</packagename>
>                                               </packagenames>
>                                               
> <defaultExcludesNamespace>true</defaultExcludesNamespace>
>                                               
> <defaultNamespacePackageMapping>true</defaultNamespacePackageMapping>
>                                               <wsdlLocation></wsdlLocation>
>                                               <frontEnd>jaxws</frontEnd>
>                                               <dataBinding>jaxb</dataBinding>
>                                               <wsdlVersion>1.1</wsdlVersion>
>                                               <catalog>catalog</catalog>
>                                               
> <extendedSoapHeaders>true</extendedSoapHeaders>
>                                               
> <validateWsdl>true</validateWsdl>
>                                               
> <serviceName>serviceName</serviceName>
>                                               
> <autoNameResolution>true</autoNameResolution>
>                                               
> <noAddressBinding>true</noAddressBinding>
>                                       </defaultOptions>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to