Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF » [emf] don't use other edit plug-ins as delegated resource locators
[emf] don't use other edit plug-ins as delegated resource locators [message #765664] Wed, 14 December 2011 13:34 Go to next message
Knut Wannheden is currently offline Knut WannhedenFriend
Messages: 298
Registered: July 2009
Senior Member
Hi all,

I have a GMF diagram editor which displays elements of an EPackage "A". This
EPackage has references to a few other EPackages. But the diagram doesn't need
to display instances of any EClasses in these references EPackages. So I don't
want to generate the edit code for these other EPackages.

Yet when I generate the edit code for my EPackage "A" the generated class
AEditPlugin will in its constructor contain references to the edit plug-in
classes of the referenced EPackages.

Is it under these circumstances safe to delete these references and change the
constructor to:

public AEditPlugin() {
super(new ResourceLocator[0]);
}

?

Regards,

--knut
Re: [emf] don't use other edit plug-ins as delegated resource locators [message #893794 is a reply to message #765664] Thu, 05 July 2012 14:04 Go to previous messageGo to next message
Knut Wannheden is currently offline Knut WannhedenFriend
Messages: 298
Registered: July 2009
Senior Member
Hi again,

Has anyone else encountered this?

Regards,

--knut

On 12/14/11 2:34 PM, Knut Wannheden wrote:
> Hi all,
>
> I have a GMF diagram editor which displays elements of an EPackage "A". This
> EPackage has references to a few other EPackages. But the diagram doesn't need
> to display instances of any EClasses in these references EPackages. So I don't
> want to generate the edit code for these other EPackages.
>
> Yet when I generate the edit code for my EPackage "A" the generated class
> AEditPlugin will in its constructor contain references to the edit plug-in
> classes of the referenced EPackages.
>
> Is it under these circumstances safe to delete these references and change the
> constructor to:
>
> public AEditPlugin() {
> super(new ResourceLocator[0]);
> }
>
> ?
>
> Regards,
>
> --knut
Re: [emf] don't use other edit plug-ins as delegated resource locators [message #893922 is a reply to message #893794] Fri, 06 July 2012 05:44 Go to previous message
Ed Merks is currently offline Ed MerksFriend
Messages: 30372
Registered: July 2009
Senior Member
Knut,

Comments below.

On 05/07/2012 4:04 PM, Knut Wannheden wrote:
> Hi again,
>
> Has anyone else encountered this?
>
> Regards,
>
> --knut
>
> On 12/14/11 2:34 PM, Knut Wannheden wrote:
>> Hi all,
>>
>> I have a GMF diagram editor which displays elements of an EPackage
>> "A". This
>> EPackage has references to a few other EPackages. But the diagram
>> doesn't need
>> to display instances of any EClasses in these references EPackages.
>> So I don't
>> want to generate the edit code for these other EPackages.
>>
>> Yet when I generate the edit code for my EPackage "A" the generated
>> class
>> AEditPlugin will in its constructor contain references to the edit
>> plug-in
>> classes of the referenced EPackages.
Do the other GenModels for those other packages have their Edit
Directory set?
>>
>> Is it under these circumstances safe to delete these references and
>> change the
>> constructor to:
>>
>> public AEditPlugin() {
>> super(new ResourceLocator[0]);
>> }
The reflective one can kick in when there aren't generated ones; you
don't even need them in the properties view when displaying the value
choices?
>>
>> ?
>>
>> Regards,
>>
>> --knut
>
>
Previous Topic:[CDO] Encounter java.lang.OutOfMemoryError: GC overhead limit exceeded when commit from 4 clients
Next Topic:OutOfMemoryError when saving resource
Goto Forum:
  


Current Time: Sat Aug 24 08:49:12 GMT 2019

Powered by FUDForum. Page generated in 0.01916 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top