ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J.W. Janssen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACE-523) Client REST API does not interpret same filters as Gogo commands
Date Thu, 28 Jan 2016 10:56:39 GMT

     [ https://issues.apache.org/jira/browse/ACE-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

J.W. Janssen updated ACE-523:
-----------------------------
    Labels: ace-next  (was: )

> Client REST API does not interpret same filters as Gogo commands
> ----------------------------------------------------------------
>
>                 Key: ACE-523
>                 URL: https://issues.apache.org/jira/browse/ACE-523
>             Project: ACE
>          Issue Type: Bug
>          Components: Client Repository
>    Affects Versions: 2.0.1
>            Reporter: J.W. Janssen
>            Assignee: J.W. Janssen
>            Priority: Minor
>              Labels: ace-next
>
> When creating an association using the Gogo commands, you can specify a cardinality of
{{N}} as shortcut for {{Integer.MAX_VALUE}}. This does not work when creating associations
through the REST API. This is trivial to add to make both APIs work in a similar manner.
> In addition, the REST API allows you to specify {{left}} and {{right}} as alternative
for {{leftEndpoint}} and {{rightEndpoint}}. Not sure what the exact meaning of this is and
why this isn't implemented in the Gogo commands...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message