Alright, to sum up the solution: Play lets you serve your assets in two different ways. The old fashioned and the new fingerprinted method introduced with sbt-web. In either case make sure you use right call in your view files: Fingerprinted assets This is the recommended way to serve assets in play. Fingerprinted assets make … Read more
If you have x as Option[Long], x.get will give you Long.
Spray is production ready, but the development team (Mathias Doenitz) works for Typesafe on Akka-http now. The status of Akka-http is “development preview”. There are vague promises of a full release “within a few months”, but nothing you can take to the bank. Edited 29-July-2015: The status of Akka-HTTP is now “release candidate” with version … Read more
As of Play 2.0, the eclipse folder and launchers are no longer generated when you run play eclipsify. After running play eclipsify, you can debug your project in Eclipse as follows: In a console outside of eclipse, run play debug run. In Eclipse, right-click your project, then choose Debug As -> Debug Configurations… Right-click Remote … Read more
If you are coming from a MVC background then Play will feel the most familiar. Lift is not MVC and it takes some time to wrap your head around it. There is no reason that you can’t use Scala with a Java-based framework like Jersey, Spring MVC, Dropwizard, Restlet, RESTEasy, etc. Or you could use … Read more
“Boxed Error” is Scala’s response to an Error being thrown within a Future. In Java, and hence Scala, subclasses of type Error have a special meaning as Fatal errors. See Differences between Exception and Error. In short, the javadoc says: An Error is a subclass of Throwable that indicates serious problems that a reasonable application … Read more
You need to specify the arguments as separate Strings: new ProcessBuilder(“cmd”, “arg1”, “arg2”, …); The constructor accepts String, varargs, and List<String>. See ProcessBuilder documentation.
I used an @ before the second if : @if (true) { … } else { @if (true) { … } else { … }}
You could use a module called SecureSocial. https://github.com/jaliss/securesocial/ This one is quite refined and many people in Play community seem to be aware/using this module. For authorization might be useful. https://github.com/schaloner/deadbolt-2/ For end to end scala stuff, https://github.com/t2v/play20-auth
You are gonna to dig yourself… deep 🙂 Simplest and most clean approach with no any doubt is creating a single application serving data for both, BE and FE, where you differ response (JSON vs HTML) by the URL, pseudo routes: GET /products/:id controllers.Frontend.productHtml(id) GET /backend/products/:id controllers.Backend.productJson(id) Benefits: single deployment (let’s say to Heroku) name … Read more