0

Is there any way not to describe every model in Play? When using Ebean I wind up writing the definition of the Finder in every model:

public static Finder<Long,Task> find = new Finder<Long,Task>(
    Long.class, Task.class
  );

also I usually declare the methods all, create, delete, update and a couple more, according to the circumstances.

public static List<Task> all() {
    return Task.find.all();
}

public static void create(Task task) {
    task.save();
}
...

I was wondering if it is possible to define all this stuff just once and then if a model needs some different functionality just re-declare it just for the model that needs it. I tried to declare a parent class for the models using generics CustomModel, and apparently java doesn't like generic methods to be static which is understandable. So is this even possible? I did that in PHP a while ago.

I'm new to Play and Java in general and I would be very thankful if anyone could help me with that.

Thank you guys!

alexg
  • 902
  • 11
  • 37

1 Answers1

2

Because of the type erasure in Java, Finder will loose Long and Task during compilation and not know about them during runtime which makes it really hard to make such an abstraction.

There is no problem using generics with statics in Java but you have to understand what scope you are in. A static method cannot access parameterized types from the class it is defined in since that would require an actual instance of the class.

One idea could be to create a non-static helper class that only takes one type parameter (the entity type) and the .class of it to its constructor and creates the finder and can have methods that implement common operations. Then create a static instance of that inside all your entities.

johanandren
  • 11,249
  • 1
  • 25
  • 30
  • thank you, do you happen to have more info on that idea? I found a module for controllers that does more or less what I need [here](https://github.com/njin-fr/play2-crud) – alexg Sep 26 '13 at 02:46
  • 1
    From a fast scan through their docs that module probably implements something like I described. So if you decide to not use the plugin, do checkout how they have implemented ther Crud class. – johanandren Sep 27 '13 at 11:58
  • will do, I would prefer doing something similar to this: http://www.playframework.com/documentation/1.0.1/crud too bad they don't have it for play 2 yet. – alexg Sep 27 '13 at 17:43