atlanmod / emfviews Goto Github PK

Bonjour,
I also tried to install EMFViews in Eclipse 2018-09 from the update site, but it fails because it depends on org.eclipse.m2m.atl.core.emf [3.8.0, 4.00), but precisely Eclipse 2018-09 installs ATL version 4.0.0.
In MegaM@Rt project we are using as baseline Eclipse for the integrated platform this 2018-09 version. Could be possible you upgrade EMFViews to be compatible with this version and provide a new update site?

Merci beaupcoup
Yosu

Bonjour,
I've followed the installation instructions to build EMFViews from Git sources, using Maven. However, the Maven build fails because of a missing dependency:
[ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: org.atlanmod.emfviews.tests 0.3.0.qualifier [ERROR] Missing requirement: org.atlanmod.emfviews.tests 0.3.0.qualifier requires 'bundle org.atlanmod.sexp2emf 0.1.0' but it could not be found
Bien cordialement
Yosu

Hi,
I downloaded myFirstViewTutorial from examples folder.
With Eclipse Kepler SR2, Epsilon 1.1_SR1 and EMF Views 0.2.0.201407021945 on Windows, I was unable to open the publicationsAndBooks.eviewtype file using EMF Views Editor due a problem with paths. Opening the file with the text editor, I had to manually change the publicationsAndBooks.eviewtype file from:

contributingMetamodels=myFirstViewTutorial/metamodels/Publication.ecore,myFirstViewTutorial/metamodels/Book.ecore
correspondenceModel=myFirstViewTutorial/viewtypes/publicationsAndBooks.xmi
correspondenceModelBase=myFirstViewTutorial/viewtypes/publicationsAndBooks.ecl
filtersMetamodel=/myFirstViewTutorial/viewtypes/publicationsAndBooks.ecore

to:

contributingMetamodels=/myFirstViewTutorial/metamodels/Publication.ecore,/myFirstViewTutorial/metamodels/Book.ecore
correspondenceModel=/myFirstViewTutorial/viewtypes/publicationsAndBooks.xmi
correspondenceModelBase=/myFirstViewTutorial/viewtypes/publicationsAndBooks.ecl
filtersMetamodel=/myFirstViewTutorial/viewtypes/publicationsAndBooks.ecore

Adding the "/" at the beginning of the paths (just like the last line "filtersMetamodel"), everything seem to work. I can not try on other operating systems, but on Windows I needed that change, otherwise I got the follow exception and the EMF Views Editor "crash":

!ENTRY org.eclipse.e4.ui.workbench 4 0 2014-09-02 15:56:44.731
!MESSAGE
!STACK 0
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: java.io.FileNotFoundException: myFirstViewTutorial\metamodels\Publication.ecore (The system cannot find the path specified)

Hello EMFViews team,

The Xtext team would like to update the Xtext community website listing all the cool projects people are building around Xtext/Xtend.

See also the corresponding GitHub issue and Bugzilla ticket.

If you are interested that the EMFViews project is listed there, please provide the following information as a comment to this issue:

<tr>
	<td><a href="project_link">project_name</a></td>
	<td>project_description_max_2_sentences</td>
	<td>license</td>
	<td>category</td>
	<td>author(s)</td>
</tr>

We will then update the Xtext community website and get it online as soon as possible.

Thanks!
Tamás

Eclipse version: Eclipse Modeling Tools Version: 2022-12 (4.26.0)

EMF Views version: 0.4.0

Branch (when relevant): master

Repeatable: Always

Problem description
When the metamodel includes some inheritance, selecting attributes from parent classes for virtualization is impossible. The problem arises both in the autocomplete function of VPDL language and when using the "*" operator that should virtualize everything from the class (including inherited attributes)

Used metamodels/models (when relevant)
The metamodel used to reproduce the problem is adapted from the one used in the EMF Views examples but includes the mentioned inheritance.
It is published in the examples repository for download if needed.

To Reproduce
Steps to reproduce the behavior:

1. Create the VPDL file like the one below:

create view getJournal as

select publications.Journal.desc,
          publications.Publications.journals,

from 'http://publications' as publications,

2. The VPDL file will raise the error indicating the inexistence of the "desc" attribute and will not generate the viewpoint. Trying publications.Publication.desc will work fine, meaning the problem with the inherited class "Journal."

3. Another option to show the problem is to try to use publications.Journal.*, which will not raise errors in the VPDL and viewpoint generation

4. See the error (screenshot below) when opening the view within MoDisco Browser. The Journal element is correctly virtualized but contains no attribute from the parent class.

Expected behavior
The view should include parent class attributes, allowing users to navigate in the view like it happens in the original model.

Screenshots

Metamodel used in the example

VPDL file with the error when trying to access inherited attributes

MoDisco browser showing only Journal attributes without the attributes from parent Publication class

Bonjour,
As I couldn't build EMFViews using Maven (see #4), I tried to import the projects into Eclipse and compile them against an Eclipse target poinited to Eclipse 2018-09 where I added the different dependencies (Epsilon, ATL, XText).
However, I have multiple issues in EMFView projects, including:

• missing source folders, such as src-gen and xtend-gen
• missing packages in declared exported-packages within the Manifest.MF

I suppose the missing packages are located in the missing source folders. I also suppose that this missing folders should be generated by Xtext, but even if I ask Eclipse to clean and compile all the projects, and they already have the XText build nature, they are not generated. Any idea?

I see also a missing dependency on org.atlanmod.sexp2emf, which seems not to be available.
Can you provide me further assistance to setup Eclipse for building EMFViews?
Merci beaupcoup
Yosu

Eclipse version: Eclipse Modeling Tools Version: 2022-12 (4.26.0)

EMF Views version: 0.4.0

Branch (when relevant): AIDOaRt

Repeatable: Always

Problem description
This issue aims to document a specific behavior of the EMF Views when dealing with inherited attributes that can lead the users to get unexpected filtered attributes. This is not a bug and usually is not problematic, but it's registered to enable possible enhancements in future versions of the EMF Views,

Used metamodels/models (when relevant)
The following metamodel was used to reproduce the problem. It can be downloaded in the examples repository together with a simple instance used in the view definition.

To Reproduce

1. Create the following VPDL file

create view example_filter as

select inherited.B[allCs, attr1],
       inherited.C.description,

from 'http://inherited' as inherited,

The view created from this VPDL file should filter out all elements of B, except for the attribute attr1 and the containment relation "allCs" (mandatory to virtualize the C objects of the model)
2. Create the .eview file with the following content

viewpoint=../src-gen/example_filter.eviewpoint
contributingModels=inherited::../../Resources/models/Issue/my_model.xmi

3. Open the view using the MoDisco model browser

4. The view includes the filtered elements and the B.description elements that should be filtered out according to the VPDL file.

Expected behavior
A view that includes only the attr1 and allCs relation. C elements that include only the "description" attribute

Screenshots
View including B.description

Additional context
It happens because the virtualization mechanism of the EMF Views is actually virtualizing the attribute A.descriptioon, a common attribute between B and C classes, creating a shared virtual element. As previously mentioned, this is not a bug but can lead to security problems, depending on the context.

IMPORTANT NOTE: This is valid only for the version compiled directly from the AIDOaRt branch and not for the main version in the master branch. If the changes were propagated, the issue will be appropriately updated when valid for the main branch.

I am using Eclipse Oxygen 1.A and cannot get the plugin to work. I have even downloaded a fresh installation of Oxygen 1.C and after installing ATL, Epsilon, and XText tried to import EMFView. Everything seems to be free of errors, however in the second Eclipse instance there is no trace of EMFView (no menu' items, no creation options, no examples). Could you please list in details on what Eclipse Packages are you running the plugins? Since Epsilon itself does not come in a bundle for Oxygen, it would be also important to know what you installed for Epsilon (version/packages of GMF, EMFatic, packages of Epsilon itself).

Thanks,

Antonio

Hello!

I tried using EMF Views and to follow the tutorial, but I was not able to create an EMF Viewtype since after completing the wizard, the Dialogue for te EMF viewtype creation stayed there. Additionally, an empty viewtype file was created.

I was as well not able to create an EMF View; the wizard could not start with the error message "The selected wizard could not be started.
Plug-in "fr.inria.atlanmod.emfviews.ui" was unable to instantiate class "fr.inria.atlanmod.emfviews.ui.wizard.view.CreateViewWizard".
fr.inria.atlanmod.emfviews.ui.wizard.view.CreateViewWizard"

yours faithfully,
Robert Bill

Eclipse version: Eclipse Modeling Tools Version: 2022-12 (4.26.0)

EMF Views version: 0.4.0

Repeatable: Always

Problem description
When using metamodels that contain references to EEnum attributes, they are not correctly virtualized by EMF Views.

Used metamodels/models (when relevant)
A slightly adapted version of the "Book" metamodel from the EMF Views example is enough to reproduce the error. It's only necessary to include a new EEnum element in the Book with few elements.

To Reproduce

Steps to reproduce the behavior:

1. Using the adapted version of the Book with the EEnum attribute, create the following VPDL file

create view publicationsAndBooks as

select book.Book.*,
       book.Chapter.*,
       book.Book join publication.Publication  as bookPublication,

from 'http://publication' as publication,
     'http://book' as book,

where s.title = t.title for bookPublication

3. Create the .eview file as usual, pointing to the models that conform to the modified version of Book and Publication metamodels.
4. Open the View using MoDisco or any other model viewer and check that the EEnum attributes are not virtualized correctly, even with no error triggered.

Expected behavior
The View should virtualize the EEnum elements.

Screenshots
The modified version of Book Metamodel

The view opened in the standard model viewer (genre is not rendered)

The view opened in MoDisco viewer (genre is rendered but as a reference instead of the values)

Eclipse version: Eclipse Modeling Tools Version: 2022-12 (4.26.0)

EMF Views version: 0.4.0

Branch (when relevant): master

Repeatable: Always

Problem description:

Altough EMF Views is just slightly dependent on Epsilon, being used just in the optional delegator, it relies on an old version of Epsilon (1.5). Automatic update of Epsilon dependency code causes compilation errors.

Steps to repeat: N/A