[jira] [Commented] (CXF-3245) Command line options are not uniform across CXF tools

["Glen Mazza (JIRA)" <ji...@apache.org>]

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

Glen Mazza commented on CXF-3245:
---------------------------------

(1) above has worked well for years with everybody, and I don't see the need to provide multiple flags to do the same thing just because Java, with its much larger pool of newbie users, decides to do something else.  

Having multiple ways to do the same thing confuses people on the mailing lists, makes Google searches less accurate, and opens up bugs in the code (because the users might erroneously specify both -cp and -classpath, for example, and because our code might be checking if a certain argument is already set (i.e., "if (cp==null)"), but if we have multiple flags we now have to make sure if *either* were set ("if cp==null || classpatch==null).  Further, it doesn't provide any benefit for the volunteer developer to work on (it's primarily busywork), and for the open source model to work properly, developers should be *strengthened* as a result of their volunteer hours on the project, not weakened by it.

So, for me, the evil of different tools providing different flags is less than maintaining multiple options to do the same thing for each tool.  I can see an advantage, however, to have greater consistency by standardizing on one command for all tools rather than retaining different variants (such as the a/addressing and db/databinding issues you mention), and in some cases it might make sense to do so in the future CXF 3.0, where backward compatibility does not need to be maintained.


> Command line options are not uniform across CXF tools
> -----------------------------------------------------
>
>                 Key: CXF-3245
>                 URL: https://issues.apache.org/jira/browse/CXF-3245
>             Project: CXF
>          Issue Type: Improvement
>          Components: Tooling
>    Affects Versions: 2.3.1
>            Reporter: Robert Liguori
>            Priority: Trivial
>         Attachments: command line options for tooling.doc
>
>
> 1) Add -classpath option to java2js and java2wsdl.
> Rationale: The java2js and java2wsdl commands use the -cp option.   Consider adding -classpath to these two commands to serve the same purpose.  Case study: java and javac support both the -cp and -classpath options.
> 2) Add -fe to java2wsdl and -frontend to wsdl2java.
> Rationale. wsdl2java supports -fe and not -frontend. java2wsdl supports -frontend and not -fe. Since the options provide the same feature, why not have command utilities support both options.
> 3) Add -address to wsdl2xml, wsdl2service, wsdl2corba and idl2wsdl. and -a to java2wsdl.
> Rationale. java2wsdl uses -address and not -a. wsdl2xml, wsdl2service, wsdl2corba and idl2wsdl use -a and not -address. Since they appear to serve the same or similar purposes (i.e., the corba address for one command differs slightly from the port address of the other command), I recommend supporting -address wherever -a is used and supporting -a wherever -address is used.
> 4) Support -db where -databinding is used and suport -databinding where -db is used. The commands java2js, java2wsdl and wsdl2java would be affected.
> 5) Examine and streamline the use of the -o option. Consider supporting the -output flag where ever this is used, if appropriate.
> Please examine the supporting spreadsheet for more information.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira