2

I'm trying to send a List of Infoobjects to my controller. I need to specify the routes file. I know how to send int,string and long as parameters, but how about a List<>?

I have tried with this, but it's not working and i'll get an error message saying "not found: type Infoobject".

GET    /generateExcel                  controllers.Application.generateExcel(list:List[Infoobject])

Thanks!

Kungen
  • 607
  • 1
  • 11
  • 24
  • I think wrong approach conceptually.. You're trying to send a list of heavy objects via a URL!! That's strange. You'd be MUCH better of storing them in a POST – cjds Jul 08 '13 at 10:24
  • @Kugen approach totaly make sence, it's an abstraction, what you receive from the get request should not be primitive type like String. – Guillaume Massé Oct 30 '13 at 15:22

2 Answers2

3

First of all, I think you need to put the package of your object in the [] of the list : List[path.of.your.package.Infoobject] (there are no imports in your routes).

Anyway, I think you can only put String and Numerals in the URL, in order to send arguments to your controllers.

1rst workaround : You can create a QueryStringBindable that binds your object (List[Infoobject]) to a string, so that the information sent via URL as a String is recovered by your controller as a List[Infoobject].

2nd workaround : Your can send Strings that could help you recreate the List in you controller (If you query the database for example, or if it's a List of object that only contains String attributes)

Here is the java doc for the QueryStringBindable : http://www.playframework.com/documentation/api/2.1.1/java/play/mvc/QueryStringBindable.html

Saffron
  • 682
  • 6
  • 14
  • This question is related to [This question](http://stackoverflow.com/questions/17482984/play-framework-controller-action-runs-every-load) and the first answer. If this is the wrong way of doing this, please try to answer the question I linked to. – Kungen Jul 08 '13 at 11:54
0

Routes aren't best place for passing complicated objects, instead of passing a List (as other pointed yet in answers/comments) you would do better by sending a comma separated list of id's of the objects persisted in the database. Remember, that in many places you can hit the wall ie. limit of the query's length or something.

If you can't/don't want to persist them in DB you can also just use a Cache API for storing whole list in the memory between the requests, so you can send in the url the ID of the cache entry as a common String.

biesior
  • 55,576
  • 10
  • 125
  • 182