Yes, mostly. @POJO only has the no-GroovyObject effect when paired with @CompileStatic. A @POJO subclass of a normal Groovy superclass still inherits the superclass’s GroovyObject methods, so it won’t become a true plain POJO. And annotating interfaces with @POJO is unnecessary/redundant.