How to register ebean Controllers (preInsert, postLoad, etc) ?

[Gyorn]

Hi,

I'm having a hard time trying to execute some Post* and Pre* action to my entities. What is the proper way to do this with ebean ?

I've found this, from the demo projet of ebean doc (https://github.com/ebean-orm-demo/demo-order/blob/master/src/main/java/app/data/OrderController.java) :

And this from the ebean API (http://www.avaje.org/static/javadoc/pub/index.html) :

"A no operation implementation of BeanPersistController. Objects extending this need to only override the methods they want to."
"A BeanPersistAdapter is either found automatically via class path search or can be added programmatically via ServerConfig.add(BeanPersistController) orServerConfig.setPersistControllers(java.util.List)."

But I can't make it work with Play. The controller won't get registered by himself, and I don't know how to retrieve the ServerConfig instance to add them manualy. For information i have a Document and DocumentController in the same package (models)

[Kevin Bosman]

Create a BeanPersistAdapter derivative, and add the fully qualified
class name to the ebean.default key in your application.conf file.
By default it reads models.*

So eg. you would need to change it to:
ebean.default="models.*,models.adapters.OrderPersistAdapter"

[Gyorn]

Thanks ! it works :)

But it's a bit weird that we have to add the fully qualified class name in the app.conf...  models.adapters.* sould be enough ..

[Kevin Bosman]

> But it's a bit weird that we have to add the fully qualified class name in
> the app.conf...  models.adapters.* sould be enough ..

Play checks for those classes matching the wildcard that have the
annotations @Entity or @Embeddable. If you think about it, that
actually makes a lot of sense, because you can't be guaranteed that
everything in your models package is going to be an ebean class.
PersistAdapter and some others don't have annotations, so it's a small
price to pay imho.

[Gyorn]

Yeah you're probably right. It's just that I didn't expected it because of the ebean API doc, where they say :  "A BeanPersistAdapter is either found automatically via class path search or can be added programmatically"

To avoid putting every adapter in the application.conf, wich could lead to many prolems, i've found this adapter :

http://dominikdorn.com/2012/01/jpa-entity-listener-annotations-avaje-ebean/ 

[Kevin Bosman]

> It's just that I didn't expected it because of
> the ebean API doc, where they say :  "A BeanPersistAdapter is either found
> automatically via class path search or can be added programmatically"

Yes, that threw me too when I first went through that.

> To avoid putting every adapter in the application.conf, wich could lead to
> many prolems, i've found this adapter :
> http://dominikdorn.com/2012/01/jpa-entity-listener-annotations-avaje-ebean/

That's pretty cool. Thanks for the link!

[julien Tournay]

Hi,

Play could also look for instances of BeanPersistAdapter.

Maybe you should suggest that in lighthouse.

jto.

[Joscha Feth]

> To avoid putting every adapter in the application.conf, wich could lead to

> many prolems, i've found this adapter :
> http://dominikdorn.com/2012/01/jpa-entity-listener-annotations-avaje-ebean/

That's pretty cool. Thanks for the link!

The link seems to be down, but I could find the gist named in that article - for future reference: https://gist.github.com/1547244