You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@ace.apache.org by "J.W. Janssen (JIRA)" <ji...@apache.org> on 2015/10/28 15:35:27 UTC

[jira] [Created] (ACE-523) Client REST API does not interpret same filters as Gogo commands

J.W. Janssen created ACE-523:
--------------------------------

             Summary: 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


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)