It's strange that oper.type.name fails in that way if oper.type is defined.

Could you set up a minimal example that reproduces the problem?

http://eclipse.org/epsilon/doc/articles/minimal-examples/

Patricia,

Wanted to give a go at this but I didn't saw the launch configuration on your minimal example. Could you please add this?

Hi Patricia,

I did some debug printing, you can try this:

	// Operations of the class [%=currentClass.name%]
	[%currentClass.println("class ");%]
	[% for (oper in currentClass.AllOperations) {%]
		[% oper.println("oper ");	%]
		[% oper.type.println("type ");	%]
  		 [%=oper.visibility%] [%=oper.type%]  [%=oper.name%] () {
  		}   	
    [%}%]

And I got:

...
oper Operation [name=addAlumno, qualifiedName=Data::Grupo::addAlumno, visibility=public, isLeaf=false, isStatic=false, concurrency=sequential, isAbstract=false, isOrdered=false, isQuery=false, isUnique=true, lower=1, upper=1]
type 
class Class [name=Profesor, qualifiedName=Data::Profesor, visibility=public, isLeaf=false, isAbstract=false, isFinalSpecialization=false, isActive=false, ]
oper Operation [name=vincular_departamento, qualifiedName=Data::Profesor::vincular_departamento, visibility=public, isLeaf=false, isStatic=false, concurrency=sequential, isAbstract=false, isOrdered=false, isQuery=false, isUnique=true, lower=1, upper=1]
...

So the addAlumno has no type, but the vincular_departamento does.

Looking at the uml model, addAlumno has no return type (probably void?) while the vincular_departamento operation has a boolean return type. So I guess the operation type is null if the operation has no return parameter. Guess you have to add some logic to test this and set the java operation return type to null if the uml operation's type is null.

In the future using this "debug printing" can help you understand what is happening (if you don't know a lot about models and decide to run the egl in debug mode )

Hope this solves your problem,