Bug 549274 - [xml] XML model does not resolve proxies
Summary: [xml] XML model does not resolve proxies
Status: NEW
Alias: None
Product: QVTd
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-15 08:56 EDT by Ed Willink CLA
Modified: 2019-07-16 09:06 EDT (History)
0 users

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 Ed Willink CLA 2019-07-15 08:56:09 EDT 
Attempting to drw a Sirius diagram of a *.oclas fails since the internal proxies are not resolved.
Comment 1 Ed Willink CLA 2019-07-15 09:20:02 EDT 
(In reply to Ed Willink from comment #0)
> ... since the internal proxies are not resolved.

This is intentional so that the proxy text appears in the XML diagram.
Comment 2 Ed Willink CLA 2019-07-16 09:06:24 EDT 
There seem to be some confusing factors.

The Create Viewpoints menu action only shows in the Model Explorer.

The Create Viewpoints menu action only shows in Model-natured projects.

The Create Viewpoints menu action only shows the Viewpoints for which there are M files applicable to the Viewpoints.

The Model Explorer may need encouragement to refresh and show a newly added model file with a M decoration.

XML diagrams auto-populate in a nested Eclipse but not outer Eclipse.

Use of *.xmlmodel is not obvious. Rename any XMI file to *.xmlmodel to have it opened as a XML-elemented rather than Model-elemented resource.

?? SaveAS *.xmlmodel may be ignored unless the prevailing XXXResources is displaved vt XMLmodelResource ?? - true for Save Abstract Syntax. But apart from debugging what save the XML-elemented XML serialzation ?

(See the XMLplay nested Eclipse project on my laptop for a working setup.)