Community
Participate
Working Groups
AQL only supports Sequences and Set as collection types, because of this any Java service defined by the end user which returns a "Collection<SomeEClass>" will be considered as a plain Java type (java.lang.Collection) hence defeating any usefull diagnostic during validation. We might want to make sure that any services provide "by default" is conform with this constraint or the end user is getting a poor validation bu default. We might also want to make sure that the documentation is clear regarding the use of List<> and Set<> in the services as the prefered return type in order to get the best validation possible.
New Gerrit change created: https://git.eclipse.org/r/97240
Gerrit change https://git.eclipse.org/r/97240 was merged to [master]. Commit: http://git.eclipse.org/c/sirius/org.eclipse.sirius.git/commit/?id=6eea0a95fbcc795a2a1d52355a6ec217d5ecdb28
Apparently a first patch was merged in M7. Moving to 5.1 to finish the work (reviewing the services shipped with Sirius, and completing the documentation). Marking as backport candidate, especially if in the end only the documentation is impacted.
New Gerrit change created: https://git.eclipse.org/r/104663
Gerrit change https://git.eclipse.org/r/104663 was merged to [master]. Commit: http://git.eclipse.org/c/sirius/org.eclipse.sirius.git/commit/?id=ea1316115f20fadc0f4a860042ef62c45c2ad6d3
Can not be verified: missing or incomplete reproduction information.
Steps to validate: 1. The documentation on using services from AQL expressions should mention clearly that the generic type "Collection" should not be used in service methods signatures. Only "List" or "Set" should be used to ensure good compatibility with AQL. 2. The standard services we provide in Sirius itself should follow these recommendations. This includes mainly org.eclipse.sirius.ext.emf.edit.EditingDomainServices and the Java services defined in our sample modelers (the 3 "basicfamily" examples).
Available in Sirius 5.1.0, see https://wiki.eclipse.org/Sirius/5.1.0.