Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc)  » [EEF] Issue with
[EEF] Issue with [message #660537] Fri, 18 March 2011 19:52 Go to next message
Eclipse User
Originally posted by: jconlon.apache.org

Have generated an EMF model and a standard EMF editor from the kml
schemas at
http://schemas.opengis.net/kml/2.2.0/

would like to use EEF (0.8.2) to make the standard emf editor more user
friendly.

Unfortunately have encountered a couple problems generating the EEF
architecture and am sort of stuck on the second one.

1. First problem is related to
https://bugs.eclipse.org/bugs/show_bug.cgi?id=339123 which I worked
around it with a global replace of the wrongly generated class name. So
far so good.

2. Second problem is that I also am see code generated in several places
in several classes for a class called EStringToStringMapEntry (Looks a
bit similar to the bug 339123 wonder if a similar work around tactic is
in order?).

Since this class does does not exist I of course get a bunch of errors
(170 + errors) show up with messageslike:

Description Resource Path Location Type EStringToStringMapEntry cannot
be resolved to a type
DocumentRootPropertiesEditionPartImpl.java
/com.verticon.google.kmlgx.core.model.edit/src-gen/com/verti con/google/kmlgx/parts/impl
line 175 Java Problem

Here is a snip from the initPart method of a generated component class
called AtomRootPropertiesEditionComponent (which extends
StandardPropertiesEditionComponent)


public void initPart(java.lang.Class key, int kind, EObject elt,
ResourceSet allResource) {
...

public boolean select(Viewer viewer, Object parentElement, Object
element) {
return (element instanceof String && element.equals("")) || (element
instanceof EStringToStringMapEntry); //$NON-NLS-1$
}



Any help or tips would be very appreciated.

thanks for the great project,

John
Re: [EEF] Issue with [message #665100 is a reply to message #660537] Wed, 13 April 2011 05:21 Go to previous messageGo to next message
Stephane Bouchet is currently offline Stephane Bouchet
Messages: 254
Registered: July 2009
Senior Member
John,


Sorry for the long delay,

To be short, please give a try to EEF 0.9.0, which contains a lots of
bugfixes. We are currently stable enough with 0.9.0RC4.

if you still have problems with your usecase, please respond in this forum.

Le 19/03/2011 00:52, John E. Conlon a écrit :
> Have generated an EMF model and a standard EMF editor from the kml
> schemas at
> http://schemas.opengis.net/kml/2.2.0/
>
> would like to use EEF (0.8.2) to make the standard emf editor more user
> friendly.
>
> Unfortunately have encountered a couple problems generating the EEF
> architecture and am sort of stuck on the second one.
>
> 1. First problem is related to
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=339123 which I worked
> around it with a global replace of the wrongly generated class name. So
> far so good.
>
> 2. Second problem is that I also am see code generated in several places
> in several classes for a class called EStringToStringMapEntry (Looks a
> bit similar to the bug 339123 wonder if a similar work around tactic is
> in order?).
>
> Since this class does does not exist I of course get a bunch of errors
> (170 + errors) show up with messageslike:
>
> Description Resource Path Location Type EStringToStringMapEntry cannot
> be resolved to a type
> DocumentRootPropertiesEditionPartImpl.java
> /com.verticon.google.kmlgx.core.model.edit/src-gen/com/verti con/google/kmlgx/parts/impl
> line 175 Java Problem
>
> Here is a snip from the initPart method of a generated component class
> called AtomRootPropertiesEditionComponent (which extends
> StandardPropertiesEditionComponent)
>
>
> public void initPart(java.lang.Class key, int kind, EObject elt,
> ResourceSet allResource) {
> ...
>
> public boolean select(Viewer viewer, Object parentElement, Object
> element) {
> return (element instanceof String && element.equals("")) || (element
> instanceof EStringToStringMapEntry); //$NON-NLS-1$
> }
>
>
>
> Any help or tips would be very appreciated.
>
> thanks for the great project,
>
> John


--
Cheers,

Stéphane Bouchet, OBEO
Re: [EEF] Issue with [message #690963 is a reply to message #665100] Thu, 30 June 2011 09:26 Go to previous messageGo to next message
John Palof is currently offline John Palof
Messages: 14
Registered: July 2009
Junior Member
I am having the same issue:"EStringToStringMapEntry cannot be resolved to a type" in the code generated by "Generate EEF Architecture"...

It occurs in the DocumentRootPropertiesEditionComponent class in instanceof tests.
EX: return (element instanceof String && element.equals("")) || (element instanceof EStringToStringMapEntry); //$NON-NLS-1$


Out of naivety I took the suggested fix from the marker of changing EStringToStringMapEntry to org.eclipse.emf.ecore.impl.EStringToStringMapEntryImpl. Did the Indigo bundling of EEF miss the interface EStringToStringMap or do I have something missing from my project?

Here is a segment of my configuration details:
org.eclipse.acceleo (3.1.0.v20110607-0602) "Acceleo"
org.eclipse.acceleo.doc (3.1.0.v20110607-0602) "Acceleo Documentation"
org.eclipse.acceleo.examples (3.1.0.v20110607-0602) "Acceleo Examples"
org.eclipse.acceleo.sdk (3.1.0.v20110607-0602) "Acceleo"
org.eclipse.acceleo.ui.capabilities (3.1.0.v20110607-0602) "Acceleo UI capability definitions"
org.eclipse.cvs (1.3.100.v20110520-0800-7B78FHk8sF7BB7SBB5EYD5) "Eclipse CVS Client"
org.eclipse.draw2d (3.7.0.v20110425-2050-46-7w3122153603161) "Graphical Editing Framework Draw2d"
org.eclipse.egit (1.0.0.201106090707-r) "Git Team Provider"
org.eclipse.emf (2.7.0.v20110606-0949) "EMF - Eclipse Modeling Framework Runtime and Tools"
org.eclipse.emf.cdo (4.0.0.v20110608-1639) "CDO Model Repository Client"
org.eclipse.emf.cdo.server (4.0.0.v20110608-1639) "CDO Model Repository Server"
org.eclipse.emf.codegen (2.7.0.v20110606-0949) "EMF Code Generation"
org.eclipse.emf.codegen.ecore (2.7.0.v20110606-0949) "EMF Ecore Code Generator"
org.eclipse.emf.codegen.ecore.ui (2.7.0.v20110606-0949) "EMF Ecore Code Generator UI"
org.eclipse.emf.codegen.ui (2.7.0.v20110606-0949) "EMF Code Generation UI"
org.eclipse.emf.common (2.7.0.v20110605-0747) "EMF Common"
org.eclipse.emf.common.ui (2.7.0.v20110606-0949) "EMF Common UI"
org.eclipse.emf.compare (1.2.0.v20110607-2028) "EMF Compare core"
org.eclipse.emf.compare.doc (1.2.0.v20110607-2028) "EMF Compare Documentation"
org.eclipse.emf.compare.sdk (1.2.0.v20110607-2028) "EMF Compare core"
org.eclipse.emf.compare.ui.capabilities (1.2.0.v20110607-2028) "EMF Compare UI capability definitions"
org.eclipse.emf.converter (2.7.0.v20110606-0949) "EMF Model Converter"
org.eclipse.emf.databinding (1.2.0.v20110606-0949) "EMF Data Binding"
org.eclipse.emf.databinding.edit (1.2.0.v20110606-0949) "EMF Edit Data Binding"
org.eclipse.emf.doc (2.7.0.v20110606-0949) "EMF Documentation"
org.eclipse.emf.ecore (2.7.0.v20110605-0747) "EMF Ecore"
org.eclipse.emf.ecore.edit (2.7.0.v20110606-0949) "EMF Ecore Edit"
org.eclipse.emf.ecore.editor (2.7.0.v20110606-0949) "EMF Sample Ecore Editor"
org.eclipse.emf.ecoretools (1.0.0.v20110608-1633) "Ecore Tools"
org.eclipse.emf.ecoretools.doc (1.0.0.v20110608-1633) "Ecore Tools Documentation"
org.eclipse.emf.edit (2.7.0.v20110606-0949) "EMF Edit"
org.eclipse.emf.edit.ui (2.7.0.v20110606-0949) "EMF Edit UI"
org.eclipse.emf.eef.codegen.ecore (1.0.0.v20110608-0819) "Acceleo Ecore Module Runtime Plug-in"
org.eclipse.emf.eef.edt (1.0.0.v20110608-0819) "EEF Runtime Plug-in"
org.eclipse.emf.eef.runtime (1.0.0.v20110608-0819) "EEF Runtime Plug-in"
org.eclipse.emf.mapping (2.7.0.v20110606-0949) "EMF Mapping"
org.eclipse.emf.mapping.ecore (2.7.0.v20110606-0949) "EMF Ecore Mapping"
org.eclipse.emf.mapping.ecore.editor (2.7.0.v20110606-0949) "EMF Ecore Mapping Editor"
org.eclipse.emf.mapping.ui (2.7.0.v20110606-0949) "EMF Mapping UI"
org.eclipse.emf.query (1.5.0.v20110502-1600-218Z7w311A142A1142) "EMF Model Query"
org.eclipse.emf.query.doc (1.5.0.v20110502-1600-33-8s733L466A3AE72) "EMF Model Query Documentation"
org.eclipse.emf.query.ocl (1.5.0.v20110502-1600-3--7w311A232602735) "EMF Model Query OCL Integration"
org.eclipse.emf.transaction (1.5.0.v20110502-1600-377-8s734C3E7D15D6B) "EMF Model Transaction Core"
org.eclipse.emf.transaction.doc (1.5.0.v20110502-1600-358Z8s733L466F3C6D4) "EMF Model Transaction Documentation"
org.eclipse.emf.validation (1.5.0.v20110502-1600-479-9oB56N5BBR6LCA6) "EMF Validation Framework Core"
org.eclipse.emf.validation.doc (1.5.0.v20110502-1600-35-8s733L466F3B769) "EMF Validation Framework Documentation"
org.eclipse.emf.validation.ocl (1.5.0.v20110502-1600-23-7w3121133502768) "EMF Validation Framework OCL Integration"
org.eclipse.emf.workspace (1.5.0.v20110502-1600-36-8s734C367E3CBC7) "EMF Model Transaction Workbench Integration Core"
org.eclipse.emf.workspace.doc (1.5.0.v20110502-1600-22-7w311A1238292A) "EMF Model Transaction Workbench Integration Documentation"

Thank you
Re: [EEF] Issue with [message #691073 is a reply to message #690963] Thu, 30 June 2011 12:12 Go to previous message
Ed Merks is currently offline Ed Merks
Messages: 25943
Registered: July 2009
Senior Member
John,

Comments below.


On 30/06/2011 6:26 AM, John Palof wrote:
> I am having the same issue:"EStringToStringMapEntry cannot be resolved
> to a type" in the code generated by "Generate EEF Architecture"...
>
> It occurs in the DocumentRootPropertiesEditionComponent class in
> instanceof tests. EX: return (element instanceof String &&
> element.equals("")) || (element instanceof EStringToStringMapEntry);
> //$NON-NLS-1$

The instanceof part of (element instanceof String && element.equals(""))
seems kind of redundant. A better test for the latter case would have
been EcorePackage.Literals.ESTRING_TO_STRING_MAP_ENTRY.isInstance(element).
>
> Out of naivety I took the suggested fix from the marker of changing
> EStringToStringMapEntry to
> org.eclipse.emf.ecore.impl.EStringToStringMapEntryImpl. Did the
> Indigo bundling of EEF miss the interface EStringToStringMap or do I
> have something missing from my project?
No interface is generated for the map entry. In general any EClass with
a non-null instanceTypeName won't generate an interface in Java. EEF's
generator should take that into account...
>
> Here is a segment of my configuration details:
> org.eclipse.acceleo (3.1.0.v20110607-0602) "Acceleo"
> org.eclipse.acceleo.doc (3.1.0.v20110607-0602) "Acceleo Documentation"
> org.eclipse.acceleo.examples (3.1.0.v20110607-0602) "Acceleo Examples"
> org.eclipse.acceleo.sdk (3.1.0.v20110607-0602) "Acceleo"
> org.eclipse.acceleo.ui.capabilities (3.1.0.v20110607-0602) "Acceleo UI
> capability definitions"
> org.eclipse.cvs (1.3.100.v20110520-0800-7B78FHk8sF7BB7SBB5EYD5)
> "Eclipse CVS Client"
> org.eclipse.draw2d (3.7.0.v20110425-2050-46-7w3122153603161)
> "Graphical Editing Framework Draw2d"
> org.eclipse.egit (1.0.0.201106090707-r) "Git Team Provider"
> org.eclipse.emf (2.7.0.v20110606-0949) "EMF - Eclipse Modeling
> Framework Runtime and Tools"
> org.eclipse.emf.cdo (4.0.0.v20110608-1639) "CDO Model Repository Client"
> org.eclipse.emf.cdo.server (4.0.0.v20110608-1639) "CDO Model
> Repository Server"
> org.eclipse.emf.codegen (2.7.0.v20110606-0949) "EMF Code Generation"
> org.eclipse.emf.codegen.ecore (2.7.0.v20110606-0949) "EMF Ecore Code
> Generator"
> org.eclipse.emf.codegen.ecore.ui (2.7.0.v20110606-0949) "EMF Ecore
> Code Generator UI"
> org.eclipse.emf.codegen.ui (2.7.0.v20110606-0949) "EMF Code Generation
> UI"
> org.eclipse.emf.common (2.7.0.v20110605-0747) "EMF Common"
> org.eclipse.emf.common.ui (2.7.0.v20110606-0949) "EMF Common UI"
> org.eclipse.emf.compare (1.2.0.v20110607-2028) "EMF Compare core"
> org.eclipse.emf.compare.doc (1.2.0.v20110607-2028) "EMF Compare
> Documentation"
> org.eclipse.emf.compare.sdk (1.2.0.v20110607-2028) "EMF Compare core"
> org.eclipse.emf.compare.ui.capabilities (1.2.0.v20110607-2028) "EMF
> Compare UI capability definitions"
> org.eclipse.emf.converter (2.7.0.v20110606-0949) "EMF Model Converter"
> org.eclipse.emf.databinding (1.2.0.v20110606-0949) "EMF Data Binding"
> org.eclipse.emf.databinding.edit (1.2.0.v20110606-0949) "EMF Edit Data
> Binding"
> org.eclipse.emf.doc (2.7.0.v20110606-0949) "EMF Documentation"
> org.eclipse.emf.ecore (2.7.0.v20110605-0747) "EMF Ecore"
> org.eclipse.emf.ecore.edit (2.7.0.v20110606-0949) "EMF Ecore Edit"
> org.eclipse.emf.ecore.editor (2.7.0.v20110606-0949) "EMF Sample Ecore
> Editor"
> org.eclipse.emf.ecoretools (1.0.0.v20110608-1633) "Ecore Tools"
> org.eclipse.emf.ecoretools.doc (1.0.0.v20110608-1633) "Ecore Tools
> Documentation"
> org.eclipse.emf.edit (2.7.0.v20110606-0949) "EMF Edit"
> org.eclipse.emf.edit.ui (2.7.0.v20110606-0949) "EMF Edit UI"
> org.eclipse.emf.eef.codegen.ecore (1.0.0.v20110608-0819) "Acceleo
> Ecore Module Runtime Plug-in"
> org.eclipse.emf.eef.edt (1.0.0.v20110608-0819) "EEF Runtime Plug-in"
> org.eclipse.emf.eef.runtime (1.0.0.v20110608-0819) "EEF Runtime Plug-in"
> org.eclipse.emf.mapping (2.7.0.v20110606-0949) "EMF Mapping"
> org.eclipse.emf.mapping.ecore (2.7.0.v20110606-0949) "EMF Ecore Mapping"
> org.eclipse.emf.mapping.ecore.editor (2.7.0.v20110606-0949) "EMF Ecore
> Mapping Editor"
> org.eclipse.emf.mapping.ui (2.7.0.v20110606-0949) "EMF Mapping UI"
> org.eclipse.emf.query (1.5.0.v20110502-1600-218Z7w311A142A1142) "EMF
> Model Query"
> org.eclipse.emf.query.doc (1.5.0.v20110502-1600-33-8s733L466A3AE72)
> "EMF Model Query Documentation"
> org.eclipse.emf.query.ocl (1.5.0.v20110502-1600-3--7w311A232602735)
> "EMF Model Query OCL Integration"
> org.eclipse.emf.transaction (1.5.0.v20110502-1600-377-8s734C3E7D15D6B)
> "EMF Model Transaction Core"
> org.eclipse.emf.transaction.doc
> (1.5.0.v20110502-1600-358Z8s733L466F3C6D4) "EMF Model Transaction
> Documentation"
> org.eclipse.emf.validation (1.5.0.v20110502-1600-479-9oB56N5BBR6LCA6)
> "EMF Validation Framework Core"
> org.eclipse.emf.validation.doc
> (1.5.0.v20110502-1600-35-8s733L466F3B769) "EMF Validation Framework
> Documentation"
> org.eclipse.emf.validation.ocl
> (1.5.0.v20110502-1600-23-7w3121133502768) "EMF Validation Framework
> OCL Integration"
> org.eclipse.emf.workspace (1.5.0.v20110502-1600-36-8s734C367E3CBC7)
> "EMF Model Transaction Workbench Integration Core"
> org.eclipse.emf.workspace.doc (1.5.0.v20110502-1600-22-7w311A1238292A)
> "EMF Model Transaction Workbench Integration Documentation"
>
> Thank you
>
Previous Topic:[TEXO] Containment references
Next Topic:[TEXO] Java errors in generated code
Goto Forum:
  


Current Time: Wed Jul 30 09:32:52 EDT 2014

Powered by FUDForum. Page generated in 0.01686 seconds