Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 354591 - [MWE2] Class Identifiers for Associations
Summary: [MWE2] Class Identifiers for Associations
Status: NEW
Alias: None
Product: EMFT
Classification: Modeling
Component: MWE (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-12 04:46 EDT by Daniel Mising name CLA
Modified: 2011-08-12 04:46 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 Daniel Mising name CLA 2011-08-12 04:46:55 EDT
Build Identifier: I20110613-1736

If you want to reference a class within an association, you are forced to specify a full qualified class name within a string:

in MWE2:
myProperty = "at.myproduct.module.MyClass"
in Java
public void setMyProperty(String clazz) { myProperty = Class.forName(clazz); }

It should be possible to reference class definitions as an own literal

in MWE2
myProperty = at.myproduct.module.MyClass
in Java
public void setMyProperty(Class<?> clazz) { myProperty = clazz; }

Of course the class constraints need to be checked
public void setMyProperty(Class<MyClass> clz) 
public void setMyProperty(Class<? extends MyBaseClass> clz) 
public void setMyProperty(Class<? super MyBaseClass> clz) 



Reproducible: Always

Steps to Reproduce:
1. Create a Workflow component which provides a Class<?> property
2. Try to assign a value within a MWE2 workflow