Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353981 - URI serialization with binary resources
Summary: URI serialization with binary resources
Status: CLOSED WONTFIX
Alias: None
Product: Acceleo
Classification: Modeling
Component: Core (show other bugs)
Version: 3.0.0   Edit
Hardware: PC Windows 7
: P3 normal
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-05 05:24 EDT by Laurent Goubet CLA
Modified: 2016-04-04 05:52 EDT (History)
1 user (show)

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 Laurent Goubet CLA 2011-08-05 05:24:22 EDT 
A module looking as the following :

-----
[module myModule('http://myMetamodel')/]

[template public mytemplate(myArg : TypeFromMyMetamodel)]
...
-----

ends up when reloaded with a proxy URI of the form

/myMetamodelProject/myMetamodel.ecore#//TypeFromMyMetamodel

i.e : we've lost the "logical" http-protocol URI of the metamodel in favor of the "project-relative" URI... which cannot be resolved most of the time.

Switching back to XMI serialization of the EMTL will properly use the http protocol for our proxy, making it resolveable.
Comment 1 Laurent Goubet CLA 2016-04-04 05:52:16 EDT 
This only happens with binary serialization of the compiled emtl file, and only if the target metamodel is in the workspace when developing the generation module. Since there is no means for us to influence the uri handlers during binary serialization, we do not plan on trying to fix this last case.