Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 342945 - Expression Label Mappings for Connections do not work
Summary: Expression Label Mappings for Connections do not work
Status: NEW
Alias: None
Product: GMF-Tooling
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-15 06:26 EDT by Ralph Gerbig CLA
Modified: 2011-10-20 09:52 EDT (History)
1 user (show)

See Also:

Attachments
Patch that places the VisualId of the edit part behind the parser (1.34 KB, patch)
2011-07-07 08:25 EDT, Ralph Gerbig CLA 		no flags Details | Diff
Show Obsolete (1) View All 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 Ralph Gerbig CLA 2011-04-15 06:26:53 EDT 
Build Identifier: 20110218-0911

I have a connection with an attached label. When I set the text in the gmfgraph it gets displayed in the editor. When I use an expression label mapping no text gets displayed. The ocl constraint I have is very simple just like 'hello'. When I enter an invalid expression like hello without ' I do not get an exception at runtime. This indicates that the expressions are not executed on connection creation.

Reproducible: Always
Comment 1 Ralph Gerbig CLA 2011-04-15 06:43:36 EDT 
The connection that contains the expression label has only the target feature set. Maybe this is why the bug is happening in may case.
Comment 2 Ralph Gerbig CLA 2011-07-07 08:25:18 EDT 
Created attachment 199256 [details]
Patch that places the VisualId of the edit part behind the parser

Could not test it as I always get a out of memory exception when trying to generate a generator model in my target workspace. Maybe someone els can test it.

The idea is to put the VisualID of the LabelEditPart that uses it behind its class name. This way more than one expression labels can be created for the same mapping.
Comment 3 Ralph Gerbig CLA 2011-07-07 08:27:53 EDT 
Wrong Patch. The Patch was intended for Bug 331875...

(In reply to comment #2)
> Created attachment 199256 [details]
> Patch that places the VisualId of the edit part behind the parser
> Could not test it as I always get a out of memory exception when trying to
> generate a generator model in my target workspace. Maybe someone els can test
> it.
> The idea is to put the VisualID of the LabelEditPart that uses it behind its
> class name. This way more than one expression labels can be created for the
> same mapping.
Comment 4 Michael Golubev CLA 2011-10-20 09:52:52 EDT 
severity reduced, not critical -- user always can use the custom parser as a workaround.