Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346880 - Treat EObject as OclAny in queries
Summary: Treat EObject as OclAny in queries
Status: CLOSED WONTFIX
Alias: None
Product: Acceleo
Classification: Modeling
Component: Core (show other bugs)
Version: 3.0.0   Edit
Hardware: PC Windows 7
: P3 enhancement
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-23 11:40 EDT by Stéphane Thibaudeau CLA
Modified: 2015-05-27 08:57 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stéphane Thibaudeau CLA 2011-05-23 11:40:56 EDT 
I've defined a query doSomething(EObject) and I was surprised I could not call it with a "uml.Package" for example.
I know now that the query should have been defined as doSomething(OclAny) but it could be useful to treat EObject as OclAny.
Comment 1 Stephane Begaudeau CLA 2012-02-20 08:29:30 EST 
Acceleo adds to OclAny most of the necessary operations from EObject (ancestors(), siblings() etc). I you need anything on OclAny, feel free to ask but the root type of all model element in Acceleo is OclAny not EObject so EObject should not be used as the type of anything in an Acceleo generator that is not defined on Ecore.
Comment 2 Laurent Goubet CLA 2015-05-27 08:57:35 EDT 
Closing resolved bugs