Bug 58 : Class that extends BeanControllerAdapter not being 'registered' with Ebean...
Priority 
High
Reported Version 
 
Logged By 
Rob
Status 
Fixed
Fixed Version 
1.0.2
Assigned To 
 
Product 
Ebean - core
Duplicate Of 
 
Created 
13/01/2009
Updated 
13/01/2009
Type 
Bug
 
Attachments 
No attachments

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.

 
Rob 13 Jan 11:28
Fixed in v1.0.2

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).

woResponse

Upload a file