| Feature suggestion: ability to import AQL modules [message #1747514] |
Tue, 15 November 2016 10:12  |
Eclipse User |
|
|
|
Hi,
We used to define acceleo modules containing a collection of queries. These queries, which possibly might invoke eachother, then could be called from Sirius vsps.
By this, it was not necessary to retype the same query multiple times.
It seems that Acceleo is to be replaced by AQL. However, I don't think that it is possible to import 'external' AQL modules and invoke the 'queries' defined in them. I think that the abiliy to define AQL modules, and the ability to import them would greatly improve reusability and maintenance of these specifications.
What do you think of it?
Greetings,
Wilbert Alberts
|
|
|
| Re: Feature suggestion: ability to import AQL modules [message #1747586 is a reply to message #1747514] |
Wed, 16 November 2016 04:23  |
| Eclipse User |
|
|
|
Hi.
Acceleo in general is not replaced by AQL. Acceleo continues to exist and to be maintained, and is still the "go to" solution for code generation. It's true that we now recommend AQL over Acceleo in the context of Sirius because it's a much better fit for that context (small expressions that need be be really fast and low overhead).
One of the things that make AQL fast is that it does not try to do too much. In particular it does not support external queries and modules. I don't think it would be a good idea to add that to AQL itself, as it would make it more complex and go against its primary objective.
The AQL runtime is flexible enough that it might be possible to support something like that purely on the Sirius side, so feel free to open a Sirius bugzilla. In the current state, if you need code reuse for complex queries, the best solution is to define your own Java services. They are really well supported by AQL, and you get to use all the goodness of the full Java language to factor/refactor/test your code.
Regards,
Pierre-Charles David
|
|
|
Powered by
FUDForum. Page generated in 0.03504 seconds
Home