Duplicated transactionManager property in Grails service

Question

When implementing a specialized Grails service (inherited from another concrete service class) I'm ending up with a weird duplicated transactionManager property. Here is what I get when inspecting the specialized service class:

Both service classes are annotated as @Transactional:

@Transactional(readOnly = true)
class FormularioService {
}

@Transactional(readOnly = true)
class FormularioCurriculoService extends FormularioService {
}

This behavior leads to NullPointerException's during transaction AOP.

1) How can an instance has two properties with the same name?

2) What could I do to keep services with a single transactionManager property (non-specialized service classes just don't present this kind of bug)

Answer 1

Just NEVER annotate an specialized service class with @Transactional, if the super class is already annotated.

@Transactional(readOnly = true)
class FormularioService {
}

//Don't annotate with @Transactional
class FormularioCurriculoService extends FormularioService {
}

More details at https://stackoverflow.com/a/37769357/1916198