If you implemented the interface BeanController then Ebean would automatically find your BeanController by searching the classpath.
However, if instead of implementing the interface BeanController you instead extend BeanControllerAdapter ... then Ebean does not find you controller.
This was a bug in com.avaje.ebean.server.core.BootupClasses
Changed BootupClasses so that the search included classes that extend the BeanControllerAdapter (anything assignable to BeanController).