Bugzilla – Full Text Bug Listing
| Summary: | Unable to invoke service using Collection as parameter | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] Acceleo | Reporter: | Goulwen Le Fur <goulwen.lefur> | ||||
| Component: | Core | Assignee: | Project Inbox <acceleo-inbox> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | laurent.goubet | ||||
| Version: | 3.0.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 183207 [details]
Fixes this limitation for all versions greater than Galileo
This is due to an OCL limitation (Collections are not Objects). As per the OCL 2.2(?) specification, this limitation will be removed, we're taking a step ahead and the attached patch will remove the limitation (in Acceleo) for all versions of MDT/OCL greater than Galileo's.
Fixed on HEAD and maintenance, This will be available on both 3.0.2RC1 and 3.1.0M4 |
Invoke service with Collection as service implies to create a Sequence{Sequence} it's impossible to do that with OCL