Changed naming convention in generated logic problems.

An identifier usually separated by whitespaces into name sections,
creating hierarchic names. By convention names with at most three
sections are represented in the following way:
"nameOfObject typeOfObject namespaceOfObject".

For example, the name of a relation "vertices" representing a
"reference" in class "Region" will be: 
"vertices reference Region"

1 files changed, 1 insertions, 1 deletions

diff --git a/Framework/hu.bme.mit.inf.dslreasoner.ecore2logic/src/hu/bme/mit/inf/dslreasoner/ecore2logic/EClassMapper.xtend b/Framework/hu.bme.mit.inf.dslreasoner.ecore2logic/src/hu/bme/mit/inf/dslreasoner/ecore2logic/EClassMapper.xtend
index 3949749b..82abd252 100644
--- a/Framework/hu.bme.mit.inf.dslreasoner.ecore2logic/src/hu/bme/mit/inf/dslreasoner/ecore2logic/EClassMapper.xtend
+++ b/Framework/hu.bme.mit.inf.dslreasoner.ecore2logic/src/hu/bme/mit/inf/dslreasoner/ecore2logic/EClassMapper.xtend
@@ -26,7 +26,7 @@ class EClassMapper_AllElementAsObject implements EClassMapper{
                 val classMapperTrace = new EClassMapper_AllElementAsObject_Trace

                 trace.classMapperTrace = classMapperTrace

                 for(c:classes) {

-                        val logicType = problem.add(TypeDeclaration('''class «c.name»''',c.isAbstract || c.isInterface))

+                        val logicType = problem.add(TypeDeclaration('''«c.name» class''',c.isAbstract || c.isInterface))

                         classMapperTrace.typeMap.put(c,logicType)

                 }

                 for(c:classes) {