[
https://issues.apache.org/jira/browse/UIMA-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637387#comment-13637387
]
Jim Challenger commented on UIMA-2792:
--------------------------------------
Burn, Normally I'd be pretty easy but I'd prefer --register [optional spec
file] in this case. It actually is consistent, in my mind, with the other
service calls : --modify [id or endpoint] --query [id or endpoint] etc. The
[optional spec file] is the analog of [id or endpoint] for the case where
you're registering and don't have an [id or endpoint] yet. (A non-technichal
argument as well, '--specification' is surprisingly hard to type and I use the
CLI for almost everything, rarely the API, and it saves wear-and-tear on the
hands to omit it for service testing. :)
This came about because ducc_services aka DuccServiceApi is different from the
others. It implements 6 functions (verbs) - I just couldn't bring myself to
make 6 new API/CLIs for what are very closely related functions. In the case
e.g. of "ducc_submit", there are no "verbs"; "ducc_submit" is implicitly the
verb. In the case of ducc_services, you need one of the six verbs (register,
modify, query, start, stop, unregister) plus their objects. I see the
[optional spec file] and [service id or endpoint] as the objects of those verbs.
> DUCC CLI/API SImplify and unify message and console callback
> ------------------------------------------------------------
>
> Key: UIMA-2792
> URL: https://issues.apache.org/jira/browse/UIMA-2792
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
> Reporter: Jim Challenger
> Assignee: Jim Challenger
>
> Use a single callback object with two methods in the API:
> duccout(...) - all DUCC generated messages come here
> consout(...) - all redirected console messages come here
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
