You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2016/12/04 11:02:58 UTC
[jira] [Comment Edited] (QPID-7571) Allow model to designate
operation parameters as not nullable
[ https://issues.apache.org/jira/browse/QPID-7571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15719756#comment-15719756 ]
Keith Wall edited comment on QPID-7571 at 12/4/16 11:02 AM:
------------------------------------------------------------
Mechanism work committed. Still need to walk through the model setting nullable on existing operations. Also think to flip the default so that all parameters are consider not nullable unless otherwise marked otherwise. This might produce less anontation clutter?
was (Author: k-wall):
Mechanism work committed. Still need to walk through the model setting nullable on existing parameters. Also think to flip the default so that all parameters are consider not nullable unless otherwise marked otherwise. This might produce less anontation clutter?
> Allow model to designate operation parameters as not nullable
> -------------------------------------------------------------
>
> Key: QPID-7571
> URL: https://issues.apache.org/jira/browse/QPID-7571
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
>
> Model operations accept parameters. We ought to be able to designate parameters as nullable or not. This will allow for uniform error handling, simpler UIs driven by the model and richer API docs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org