sample with play-plugins-salat can't recognize ObjectId (related to https://github.com/leon/play-salat/issues/53)

[leon]

sample with play-plugins-salat can't recognize ObjectId (related to https://github.com/leon/play-salat/issues/53)

i am having a hard time understanding how sample project use salat plugin and why it has some of the code.
For example why it has 2 controllers if all it does is showing a list of users from the database and allow to get one by Object id.

Can someone explain the architecture underneath. It's problematic to start using something without a strong knowledge of technology and any documentation. Description says very little about why I need salat plugin and how would I use it and how sample project is suppose to work

[Manc]

I've got to say, I've got the same problems. I'm quite new to Scala and Play Framework and just can't get it work.

[leon]

the magic behind theObjectId conversion lies with importing the implicit conversions for it.

Make shure you have added them in you bould.sbt or Build.scala

https://github.com/leon/play-salat/blob/master/sample/project/Build.scala#L15

[Manc]

Alright, quick update: I tried getting it work almost on a weekly basis. Today it suddenly worked!

I made sure I'm using Play 2.2.1, created a new project, carefully copied stuff from the sample to my project and I had almost no problems. It works, but I get a warning, when compiling:

[info] Compiling 14 Scala sources and 2 Java sources to …/target/scala-2.10/classes...
[warn] there were 1 feature warning(s); re-run with -feature for details
[warn] one warning found

I don't know if this is related to play-salat, I don't even know what to re-run with -feature (compile -feature is not working and starting play -feature neither).

Anyway, at least I can start doing something now. Thanks!

I think due to lack of support or documentation because nobody has time to work on both I'll drop efforts and move away to reactive-mongo - it seems to be less mature but in active development.

I think this wiki page should have a clear message at the top of it with big font saying "attention! little documentation, almost no samples, no explanation how it works and why, very brief comments - SUGGESTED NOT TO USE.

my strong opinion - if you don't do it right - don't do it at all, and don't recomment anyone to use it. I was surprised this plugin is mentioned on play framework page - there should be an indicator of how useful it is.
Apart from that - if somebody wants to play with the plugin and experiments and spend a lots of time trying to guess what's happening - you can do it, but it's not for production apps.

and by the way - lack of time is not an excuse for a good documentation : check out reactive mongo plugin for play:

https://github.com/ReactiveMongo/Play-ReactiveMongo/blob/master/samples/Play-ReactiveMongo-Sample/app/controllers/Application.scala

[leon]

The plugin works, the sample works.
I did this plugin because I needed it myself. You're not forced to use it, and if you don't like the documentation help me out by writing some better documentation. It's all about trying to help each other by not having to reinvent the wheel everytime you need something.

I can understand the frustration when something isn't well documented. But it all boils down to time and money. If your're willing to pay me, I would gladly update the documentation with more examples and inline commenting.