Home » Modeling » M2T (model-to-text transformation) » [Acceleo] Workspace ecore models URI resolution
| [Acceleo] Workspace ecore models URI resolution [message #673353] |
Mon, 23 May 2011 06:01  |
Eclipse User |
|
|
|
Hi
In either Helios or Indigo:
I have an ecore model in a project in my workspace. When I want to
create an Acceleo project then sometimes the model shows up in the
Package Selection dialog and sometimes it doesn't. What is the event
that triggers the model to show in the Package Selection dialog???
My current solution is to randomly click and open projects and files in
the workspace until the model is resolved.
Once it "magically" shows up then the URI is resolved for previously
created Acceleo projects.
-H
|
|
| | | | | |
| Re: [Acceleo] Workspace ecore models URI resolution [message #675324 is a reply to message #675217] |
Tue, 31 May 2011 03:33  |
| Eclipse User |
|
|
|
Ed,
I never told that was good practice, just that ATL provides such an
action on right-click in the workspace ^^.
Acceleo does allow for the use of metamodels that are in the workspace
instead of being installed in bundles; but we use our own package
registry for that (it actually acts as a proxy with the actual package
registry in order not to pollute the global instance).
Hugo is trying to use one of these "dynamic" metamodels in Acceleo, and
I recall that there are times when these metamodels get registered in
the global package registry, but not why : when we load one of their
dynamic instance? When we open another model that directly references
them (through a load resource)?
Laurent Goubet
Obeo
On 30/05/2011 17:47, Ed Merks wrote:
> Laurent,
>
> I'm not sure how you're populating the list. The contents of
> EPackage.Registry.INSTANCE should be initialized when the bundles are
> loaded and should not change over time (except by virtue of bundles
> loading, which typically doesn't happen dynamically). No one should be
> adding things to the global registry programmatically when running as an
> Equinox process...
>
>
> Laurent Goubet wrote:
>> Hugo,
>>
>> Ed might be a better source of information on that; you're basically
>> trying to figure out when package Xyz gets registered in the package
>> registry. Other than that, you might be interested in looking at ATL
>> that provides a workspace "right click > register metamodel" action on
>> models.
>>
>> Laurent Goubet
>> Obeo
|
|
|
| Re: [Acceleo] Workspace ecore models URI resolution [message #675330 is a reply to message #675217] |
Tue, 31 May 2011 03:33 |
| Eclipse User |
|
|
|
Ed,
I never told that was good practice, just that ATL provides such an
action on right-click in the workspace ^^.
Acceleo does allow for the use of metamodels that are in the workspace
instead of being installed in bundles; but we use our own package
registry for that (it actually acts as a proxy with the actual package
registry in order not to pollute the global instance).
Hugo is trying to use one of these "dynamic" metamodels in Acceleo, and
I recall that there are times when these metamodels get registered in
the global package registry, but not why : when we load one of their
dynamic instance? When we open another model that directly references
them (through a load resource)?
Laurent Goubet
Obeo
On 30/05/2011 17:47, Ed Merks wrote:
> Laurent,
>
> I'm not sure how you're populating the list. The contents of
> EPackage.Registry.INSTANCE should be initialized when the bundles are
> loaded and should not change over time (except by virtue of bundles
> loading, which typically doesn't happen dynamically). No one should be
> adding things to the global registry programmatically when running as an
> Equinox process...
>
>
> Laurent Goubet wrote:
>> Hugo,
>>
>> Ed might be a better source of information on that; you're basically
>> trying to figure out when package Xyz gets registered in the package
>> registry. Other than that, you might be interested in looking at ATL
>> that provides a workspace "right click > register metamodel" action on
>> models.
>>
>> Laurent Goubet
>> Obeo
|
|
|
| Re: [Acceleo] Workspace ecore models URI resolution [message #675336 is a reply to message #675217] |
Tue, 31 May 2011 03:33 |
| Eclipse User |
|
|
|
Ed,
I never told that was good practice, just that ATL provides such an
action on right-click in the workspace ^^.
Acceleo does allow for the use of metamodels that are in the workspace
instead of being installed in bundles; but we use our own package
registry for that (it actually acts as a proxy with the actual package
registry in order not to pollute the global instance).
Hugo is trying to use one of these "dynamic" metamodels in Acceleo, and
I recall that there are times when these metamodels get registered in
the global package registry, but not why : when we load one of their
dynamic instance? When we open another model that directly references
them (through a load resource)?
Laurent Goubet
Obeo
On 30/05/2011 17:47, Ed Merks wrote:
> Laurent,
>
> I'm not sure how you're populating the list. The contents of
> EPackage.Registry.INSTANCE should be initialized when the bundles are
> loaded and should not change over time (except by virtue of bundles
> loading, which typically doesn't happen dynamically). No one should be
> adding things to the global registry programmatically when running as an
> Equinox process...
>
>
> Laurent Goubet wrote:
>> Hugo,
>>
>> Ed might be a better source of information on that; you're basically
>> trying to figure out when package Xyz gets registered in the package
>> registry. Other than that, you might be interested in looking at ATL
>> that provides a workspace "right click > register metamodel" action on
>> models.
>>
>> Laurent Goubet
>> Obeo
|
|
|
| Re: [Acceleo] Workspace ecore models URI resolution [message #675342 is a reply to message #675217] |
Tue, 31 May 2011 03:33 |
| Eclipse User |
|
|
|
Ed,
I never told that was good practice, just that ATL provides such an
action on right-click in the workspace ^^.
Acceleo does allow for the use of metamodels that are in the workspace
instead of being installed in bundles; but we use our own package
registry for that (it actually acts as a proxy with the actual package
registry in order not to pollute the global instance).
Hugo is trying to use one of these "dynamic" metamodels in Acceleo, and
I recall that there are times when these metamodels get registered in
the global package registry, but not why : when we load one of their
dynamic instance? When we open another model that directly references
them (through a load resource)?
Laurent Goubet
Obeo
On 30/05/2011 17:47, Ed Merks wrote:
> Laurent,
>
> I'm not sure how you're populating the list. The contents of
> EPackage.Registry.INSTANCE should be initialized when the bundles are
> loaded and should not change over time (except by virtue of bundles
> loading, which typically doesn't happen dynamically). No one should be
> adding things to the global registry programmatically when running as an
> Equinox process...
>
>
> Laurent Goubet wrote:
>> Hugo,
>>
>> Ed might be a better source of information on that; you're basically
>> trying to figure out when package Xyz gets registered in the package
>> registry. Other than that, you might be interested in looking at ATL
>> that provides a workspace "right click > register metamodel" action on
>> models.
>>
>> Laurent Goubet
>> Obeo
|
|
|
| Re: [Acceleo] Workspace ecore models URI resolution [message #675345 is a reply to message #675217] |
Tue, 31 May 2011 03:33 |
| Eclipse User |
|
|
|
Ed,
I never told that was good practice, just that ATL provides such an
action on right-click in the workspace ^^.
Acceleo does allow for the use of metamodels that are in the workspace
instead of being installed in bundles; but we use our own package
registry for that (it actually acts as a proxy with the actual package
registry in order not to pollute the global instance).
Hugo is trying to use one of these "dynamic" metamodels in Acceleo, and
I recall that there are times when these metamodels get registered in
the global package registry, but not why : when we load one of their
dynamic instance? When we open another model that directly references
them (through a load resource)?
Laurent Goubet
Obeo
On 30/05/2011 17:47, Ed Merks wrote:
> Laurent,
>
> I'm not sure how you're populating the list. The contents of
> EPackage.Registry.INSTANCE should be initialized when the bundles are
> loaded and should not change over time (except by virtue of bundles
> loading, which typically doesn't happen dynamically). No one should be
> adding things to the global registry programmatically when running as an
> Equinox process...
>
>
> Laurent Goubet wrote:
>> Hugo,
>>
>> Ed might be a better source of information on that; you're basically
>> trying to figure out when package Xyz gets registered in the package
>> registry. Other than that, you might be interested in looking at ATL
>> that provides a workspace "right click > register metamodel" action on
>> models.
>>
>> Laurent Goubet
>> Obeo
|
|
|
| Re: [Acceleo] Workspace ecore models URI resolution [message #675347 is a reply to message #675217] |
Tue, 31 May 2011 03:33 |
| Eclipse User |
|
|
|
Ed,
I never told that was good practice, just that ATL provides such an
action on right-click in the workspace ^^.
Acceleo does allow for the use of metamodels that are in the workspace
instead of being installed in bundles; but we use our own package
registry for that (it actually acts as a proxy with the actual package
registry in order not to pollute the global instance).
Hugo is trying to use one of these "dynamic" metamodels in Acceleo, and
I recall that there are times when these metamodels get registered in
the global package registry, but not why : when we load one of their
dynamic instance? When we open another model that directly references
them (through a load resource)?
Laurent Goubet
Obeo
On 30/05/2011 17:47, Ed Merks wrote:
> Laurent,
>
> I'm not sure how you're populating the list. The contents of
> EPackage.Registry.INSTANCE should be initialized when the bundles are
> loaded and should not change over time (except by virtue of bundles
> loading, which typically doesn't happen dynamically). No one should be
> adding things to the global registry programmatically when running as an
> Equinox process...
>
>
> Laurent Goubet wrote:
>> Hugo,
>>
>> Ed might be a better source of information on that; you're basically
>> trying to figure out when package Xyz gets registered in the package
>> registry. Other than that, you might be interested in looking at ATL
>> that provides a workspace "right click > register metamodel" action on
>> models.
>>
>> Laurent Goubet
>> Obeo
|
|
|
| Re: [Acceleo] Workspace ecore models URI resolution [message #675354 is a reply to message #675217] |
Tue, 31 May 2011 03:33 |
| Eclipse User |
|
|
|
Ed,
I never told that was good practice, just that ATL provides such an
action on right-click in the workspace ^^.
Acceleo does allow for the use of metamodels that are in the workspace
instead of being installed in bundles; but we use our own package
registry for that (it actually acts as a proxy with the actual package
registry in order not to pollute the global instance).
Hugo is trying to use one of these "dynamic" metamodels in Acceleo, and
I recall that there are times when these metamodels get registered in
the global package registry, but not why : when we load one of their
dynamic instance? When we open another model that directly references
them (through a load resource)?
Laurent Goubet
Obeo
On 30/05/2011 17:47, Ed Merks wrote:
> Laurent,
>
> I'm not sure how you're populating the list. The contents of
> EPackage.Registry.INSTANCE should be initialized when the bundles are
> loaded and should not change over time (except by virtue of bundles
> loading, which typically doesn't happen dynamically). No one should be
> adding things to the global registry programmatically when running as an
> Equinox process...
>
>
> Laurent Goubet wrote:
>> Hugo,
>>
>> Ed might be a better source of information on that; you're basically
>> trying to figure out when package Xyz gets registered in the package
>> registry. Other than that, you might be interested in looking at ATL
>> that provides a workspace "right click > register metamodel" action on
>> models.
>>
>> Laurent Goubet
>> Obeo
|
|
|
| Re: [Acceleo] Workspace ecore models URI resolution [message #675356 is a reply to message #675217] |
Tue, 31 May 2011 03:33 |
| Eclipse User |
|
|
|
Ed,
I never told that was good practice, just that ATL provides such an
action on right-click in the workspace ^^.
Acceleo does allow for the use of metamodels that are in the workspace
instead of being installed in bundles; but we use our own package
registry for that (it actually acts as a proxy with the actual package
registry in order not to pollute the global instance).
Hugo is trying to use one of these "dynamic" metamodels in Acceleo, and
I recall that there are times when these metamodels get registered in
the global package registry, but not why : when we load one of their
dynamic instance? When we open another model that directly references
them (through a load resource)?
Laurent Goubet
Obeo
On 30/05/2011 17:47, Ed Merks wrote:
> Laurent,
>
> I'm not sure how you're populating the list. The contents of
> EPackage.Registry.INSTANCE should be initialized when the bundles are
> loaded and should not change over time (except by virtue of bundles
> loading, which typically doesn't happen dynamically). No one should be
> adding things to the global registry programmatically when running as an
> Equinox process...
>
>
> Laurent Goubet wrote:
>> Hugo,
>>
>> Ed might be a better source of information on that; you're basically
>> trying to figure out when package Xyz gets registered in the package
>> registry. Other than that, you might be interested in looking at ATL
>> that provides a workspace "right click > register metamodel" action on
>> models.
>>
>> Laurent Goubet
>> Obeo
|
|
|
| Re: [Acceleo] Workspace ecore models URI resolution [message #675357 is a reply to message #675217] |
Tue, 31 May 2011 03:33 |
| Eclipse User |
|
|
|
Ed,
I never told that was good practice, just that ATL provides such an
action on right-click in the workspace ^^.
Acceleo does allow for the use of metamodels that are in the workspace
instead of being installed in bundles; but we use our own package
registry for that (it actually acts as a proxy with the actual package
registry in order not to pollute the global instance).
Hugo is trying to use one of these "dynamic" metamodels in Acceleo, and
I recall that there are times when these metamodels get registered in
the global package registry, but not why : when we load one of their
dynamic instance? When we open another model that directly references
them (through a load resource)?
Laurent Goubet
Obeo
On 30/05/2011 17:47, Ed Merks wrote:
> Laurent,
>
> I'm not sure how you're populating the list. The contents of
> EPackage.Registry.INSTANCE should be initialized when the bundles are
> loaded and should not change over time (except by virtue of bundles
> loading, which typically doesn't happen dynamically). No one should be
> adding things to the global registry programmatically when running as an
> Equinox process...
>
>
> Laurent Goubet wrote:
>> Hugo,
>>
>> Ed might be a better source of information on that; you're basically
>> trying to figure out when package Xyz gets registered in the package
>> registry. Other than that, you might be interested in looking at ATL
>> that provides a workspace "right click > register metamodel" action on
>> models.
>>
>> Laurent Goubet
>> Obeo
|
|
|
| Re: [Acceleo] Workspace ecore models URI resolution [message #675358 is a reply to message #675217] |
Tue, 31 May 2011 03:33 |
| Eclipse User |
|
|
|
Ed,
I never told that was good practice, just that ATL provides such an
action on right-click in the workspace ^^.
Acceleo does allow for the use of metamodels that are in the workspace
instead of being installed in bundles; but we use our own package
registry for that (it actually acts as a proxy with the actual package
registry in order not to pollute the global instance).
Hugo is trying to use one of these "dynamic" metamodels in Acceleo, and
I recall that there are times when these metamodels get registered in
the global package registry, but not why : when we load one of their
dynamic instance? When we open another model that directly references
them (through a load resource)?
Laurent Goubet
Obeo
On 30/05/2011 17:47, Ed Merks wrote:
> Laurent,
>
> I'm not sure how you're populating the list. The contents of
> EPackage.Registry.INSTANCE should be initialized when the bundles are
> loaded and should not change over time (except by virtue of bundles
> loading, which typically doesn't happen dynamically). No one should be
> adding things to the global registry programmatically when running as an
> Equinox process...
>
>
> Laurent Goubet wrote:
>> Hugo,
>>
>> Ed might be a better source of information on that; you're basically
>> trying to figure out when package Xyz gets registered in the package
>> registry. Other than that, you might be interested in looking at ATL
>> that provides a workspace "right click > register metamodel" action on
>> models.
>>
>> Laurent Goubet
>> Obeo
|
|
|
| Re: [Acceleo] Workspace ecore models URI resolution [message #675373 is a reply to message #675217] |
Tue, 31 May 2011 03:33 |
| Eclipse User |
|
|
|
Ed,
I never told that was good practice, just that ATL provides such an
action on right-click in the workspace ^^.
Acceleo does allow for the use of metamodels that are in the workspace
instead of being installed in bundles; but we use our own package
registry for that (it actually acts as a proxy with the actual package
registry in order not to pollute the global instance).
Hugo is trying to use one of these "dynamic" metamodels in Acceleo, and
I recall that there are times when these metamodels get registered in
the global package registry, but not why : when we load one of their
dynamic instance? When we open another model that directly references
them (through a load resource)?
Laurent Goubet
Obeo
On 30/05/2011 17:47, Ed Merks wrote:
> Laurent,
>
> I'm not sure how you're populating the list. The contents of
> EPackage.Registry.INSTANCE should be initialized when the bundles are
> loaded and should not change over time (except by virtue of bundles
> loading, which typically doesn't happen dynamically). No one should be
> adding things to the global registry programmatically when running as an
> Equinox process...
>
>
> Laurent Goubet wrote:
>> Hugo,
>>
>> Ed might be a better source of information on that; you're basically
>> trying to figure out when package Xyz gets registered in the package
>> registry. Other than that, you might be interested in looking at ATL
>> that provides a workspace "right click > register metamodel" action on
>> models.
>>
>> Laurent Goubet
>> Obeo
|
|
|
| Re: [Acceleo] Workspace ecore models URI resolution [message #675374 is a reply to message #675324] |
Tue, 31 May 2011 03:46 |
| Eclipse User |
|
|
|
Hi Laurent
You've made significant progress with URI resolution since M4 so:
"and I recall that there are times when these metamodels get registered
in the global package registry, but not why"
may now be inappropriate. After Indigo, I recommend removing all global
package registrations and reviewing what breaks.
Regards
Ed Willink
On 31/05/2011 08:33, Laurent Goubet wrote:
> Ed,
>
> I never told that was good practice, just that ATL provides such an
> action on right-click in the workspace ^^.
>
> Acceleo does allow for the use of metamodels that are in the workspace
> instead of being installed in bundles; but we use our own package
> registry for that (it actually acts as a proxy with the actual package
> registry in order not to pollute the global instance).
>
> Hugo is trying to use one of these "dynamic" metamodels in Acceleo,
> and I recall that there are times when these metamodels get registered
> in the global package registry, but not why : when we load one of
> their dynamic instance? When we open another model that directly
> references them (through a load resource)?
>
> Laurent Goubet
> Obeo
>
> On 30/05/2011 17:47, Ed Merks wrote:
>> Laurent,
>>
>> I'm not sure how you're populating the list. The contents of
>> EPackage.Registry.INSTANCE should be initialized when the bundles are
>> loaded and should not change over time (except by virtue of bundles
>> loading, which typically doesn't happen dynamically). No one should be
>> adding things to the global registry programmatically when running as an
>> Equinox process...
>>
>>
>> Laurent Goubet wrote:
>>> Hugo,
>>>
>>> Ed might be a better source of information on that; you're basically
>>> trying to figure out when package Xyz gets registered in the package
>>> registry. Other than that, you might be interested in looking at ATL
>>> that provides a workspace "right click > register metamodel" action on
>>> models.
>>>
>>> Laurent Goubet
>>> Obeo
>
|
|
|
Goto Forum:
Current Time: Mon Mar 10 21:42:34 EDT 2025
Powered by FUDForum. Page generated in 0.07016 seconds |
Home