Bug 508553 - Project containing Java Services has to be open in both runtime and development Eclipse instances
Summary: Project containing Java Services has to be open in both runtime and developme...
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Core (show other bugs)
Version: 4.1.1   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: siriuscon2016
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-12-01 14:05 EST by Amine Kechaou CLA
Modified: 2017-01-20 05:28 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Amine Kechaou CLA 2016-12-01 14:05:13 EST
When using Java services in a project separate from the VSM project, we had to open this project in both the development and the runtime Eclipse instances.

If the project isn't open in the runtime instance, then the .odesign doesn't validate and does not recognize the services.
If the project isn't open in the development instance, then I get some uncaught exceptions and this sort of message when I'm trying to test the editor in a Modeling project and do actions that require the services: Class org.palladiosimulator.editors.sirius.services.PCMServices Couldn't be found in the classpath of the bundle containing module PCMServices.emtl.

We also tried to add a dependency to the plugin containing the Java Services in the plugin containing the .odesign, but that did not resolve the issue.

Here is a link to the Github repository: 
https://github.com/PalladioSimulator/Palladio-Editors-Sirius
The project containing the Java Services is org.palladiosimulator.editors.sirius.services
Comment 1 Maxime Porhel CLA 2016-12-09 05:49:23 EST
Hi Amine, 

It seems that you try to use this service from an Acceleo3 expression [yourExpressionInAcceleo3/]
Did you try this with the corresponding AQL expression aql:youExpressionTranslatedIntoAQL ? Both interpreter might not have the same rules regarding the classpath. And this particular case might not be supported by Acceleo3. 

How do you reference the project from the VSM project ? Throught plugin dependancies or Import package ? regards, 

Maxime
Comment 2 Amine Kechaou CLA 2016-12-09 06:10:18 EST
(In reply to Maxime Porhel from comment #1)
> Hi Amine, 
> 
> It seems that you try to use this service from an Acceleo3 expression
> [yourExpressionInAcceleo3/]
> Did you try this with the corresponding AQL expression
> aql:youExpressionTranslatedIntoAQL ? Both interpreter might not have the
> same rules regarding the classpath. And this particular case might not be
> supported by Acceleo3. 
> 
> How do you reference the project from the VSM project ? Throught plugin
> dependancies or Import package ? regards, 
> 
> Maxime

Hi Maxime,

Yes we tried with aql: and service: The services are only available when the project is open in both instances.

We reference the project through plugin dependencies.

Amine
Comment 3 Maxime Porhel CLA 2016-12-09 06:58:34 EST
Do you test your modeling project in a second runtime launched from the first one or in the same runtime than the VSM project ?
Comment 4 Maxime Porhel CLA 2016-12-09 07:00:56 EST
Thanks for the detailed bug report, this is an interesting improvement lead to improve the Specififer experience. 
Nevertheless, it's not yet in the scope of a future release.