ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (Closed) (JIRA)" <>
Subject [jira] [Closed] (ACE-197) association wildcards don't work in the REST api
Date Tue, 20 Mar 2012 11:53:38 GMT


Marcel Offermans closed ACE-197.

    Resolution: Cannot Reproduce
      Assignee: Marcel Offermans

When I first add a number of bundles, then add a feature, and finally create an association
between the two with the following JSON data:

{ attributes:
  { leftEndpoint: "(Bundle-SymbolicName=*)",
    leftCardinality: "10000",
    rightEndpoint: "(name=h)",
    rightCardinality: "1" },
  tags: {} }

I get an association that matches on its left hand side with (at most 10000) bundles with
a Bundle-SymbolicName and on the right hand side a feature with a name called "h".

Please note that if more bundles match than is specified in the cardinality, ACE will try
to obtain a comparator for the specific type of RepositoryObject in order to sort the list
and it will select the top matching candidates. If there is no comparator (for example, currently
features are not comparable as I would not have a clue how to implement such a comparison)
you will get an error.

> association wildcards don't work in the REST api
> ------------------------------------------------
>                 Key: ACE-197
>                 URL:
>             Project: ACE
>          Issue Type: Bug
>            Reporter: Paul Bakker
>            Assignee: Marcel Offermans
> If for example the following filter is used for the left side when creating a artifact/feature
association: (Bundle-SymbolicName=*), the association is created (no errors at least) but
the artifacts are not associated. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message