Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341982 - Migrate reusable operations from Groovy to Java
Summary: Migrate reusable operations from Groovy to Java
Status: RESOLVED FIXED
Alias: None
Product: Edapt
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal
Target Milestone: ---   Edit
Assignee: Markus Herrmannsdoerfer CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-06 03:10 EDT by Markus Herrmannsdoerfer CLA
Modified: 2011-05-13 13:24 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Herrmannsdoerfer CLA 2011-04-06 03:10:10 EDT
To get rid of Groovy, we also need to migrate reusable operations from Groovy to Java. Therefore, we need to migrate the infrastructure for defining and executing operations from Groovy to Java. Finally, we also need to migrate all existing operation definitions.
Comment 1 Markus Herrmannsdoerfer CLA 2011-05-13 13:24:41 EDT
Now, reusable operations can be specified completely in Java classes. These classes have to inherit from OperationImplementation which provides basic methods to deal with reusable operations. Moreover, this super class provides an interface for implementing reusable operations. The different constituents of reusable operations like parameters, constraints, and so on, are marked by Java annotations. Libraries which are implemented by separate classes provide a means to organize a large set of operations.