[EMF & Teneo] Generating Java Packages for Ecore Packages with only subpackages [message #422888] |
Wed, 17 September 2008 20:48  |
Eclipse User |
|
|
|
I just noticed that no Java EPackage classes get generated for ecore
packages that have no classes in it. I have a set of these which contain
sub packages only. These subpackages may contain classes though. I was
hoping that by having a heirarchy of ecore packages I could give just the
top level package to Teneo. Not sure if that would work anyway,
admittedly. Either way is there a way to turn on generation of packages in
this case.
Background
----------
I'm in the process of splitting a large ecore model into several smaller
ones.
The original came from an import from an XSD and has around 900 classes in
the one package. This is a pain to deal with as there is an overwhelming
number of classes in one package (the old needle in a haystack problem)
and the performance is close to unusable as every time I save a change
that affects the model eclipse locks up for around a minute with
'Synchronizing EMF resources'
I'm splitting it up using a simple class based on pattern matching on the
class name. It splits into a hierarchical model as follows:
- each ecore package has its own ecore file.
- the ecore file contains the package as its sole top level element
- the package contains all the classes at that level (if any) and any sub
packages.
- obviously it follows from point 1 that the sub packages are
effectively short cuts.
This means I still end up with a top ecore model where I can navigate the
whole model by following the short cuts of sub packages, but I can also
just open a child ecore model and work with that.
I had hoped at this point that I could just hand the top level package to
Teneo and have it navigate the whole model magically.
Unfortuantely, no Java packages (i.e. subtypes of EPackage) are being
created for packages that have no direct child classes.
Is there a way to turn this on?
|
|
|
|
|
Re: [EMF & Teneo] Generating Java Packages for Ecore Packages with only subpacka [message #422960 is a reply to message #422929] |
Fri, 19 September 2008 12:10  |
Eclipse User |
|
|
|
Andrew,
Yes, given the ~100 items on the wishlist, it's not percolated its way
onto the very limited work queue, particularly given that a dummy
EDataType is a pretty easy workaround...
Andrew H wrote:
> OK thanks Ed. I've added a comment and my vote. I take it that this
> issue is not a high priority given the date it was logged.
>
> Ed Merks wrote:
>
>> Andrew,
>
>> This is
>> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=142856>
>
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=142856
>
>> You could put a dummy EDataType in there so that it's not empty.
>
>
>> Andrew H wrote:
>>> I just noticed that no Java EPackage classes get generated for ecore
>>> packages that have no classes in it. I have a set of these which
>>> contain sub packages only. These subpackages may contain classes
>>> though. I was hoping that by having a heirarchy of ecore packages I
>>> could give just the top level package to Teneo. Not sure if that
>>> would work anyway, admittedly. Either way is there a way to turn on
>>> generation of packages in this case.
>>>
>>> Background
>>> ----------
>>>
>>> I'm in the process of splitting a large ecore model into several
>>> smaller ones.
>>> The original came from an import from an XSD and has around 900
>>> classes in the one package. This is a pain to deal with as there is
>>> an overwhelming number of classes in one package (the old needle in
>>> a haystack problem) and the performance is close to unusable as
>>> every time I save a change that affects the model eclipse locks up
>>> for around a minute with 'Synchronizing EMF resources'
>>>
>>> I'm splitting it up using a simple class based on pattern matching
>>> on the class name. It splits into a hierarchical model as follows:
>>>
>>> - each ecore package has its own ecore file.
>>> - the ecore file contains the package as its sole top level element
>>> - the package contains all the classes at that level (if any) and
>>> any sub packages.
>>> - obviously it follows from point 1 that the sub packages are
>>> effectively short cuts.
>>>
>>> This means I still end up with a top ecore model where I can
>>> navigate the whole model by following the short cuts of sub
>>> packages, but I can also just open a child ecore model and work with
>>> that.
>>>
>>> I had hoped at this point that I could just hand the top level
>>> package to Teneo and have it navigate the whole model magically.
>>>
>>> Unfortuantely, no Java packages (i.e. subtypes of EPackage) are
>>> being created for packages that have no direct child classes. Is
>>> there a way to turn this on?
>>>
>>>
>>>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.08190 seconds