playframework-2.3

In a typical web application, there are some things that I would prefer to run as delayed jobs/tasks . They tend to have some or all of the following properties: Takes a long time (anywhere from multiple seconds to multiple minutes to multiple hours). Occupy some resource heavily (CPU, network, disk, external API limits, etc.) Result not immediately necessary. Can complete HTTP response without it. OK (and possibly even preferable) to delay until later. Can be (and possibly preferable to) run on (a) different machine(s) than web server(s). The machine(s) are potentially dedicated job/task

I have seen a few questions on this but cant seem to get to the bottom of it. I have a Play Framework 2.3.7 (Activator 1.2.12) site, when I run it in dev mode everything works fine. When I start it in production mode I get the following errors: [app] $ start [info] Wrote C:\Users\App\git\website2.0\target\scala-2.10\app_2.10-1.0- SNAPSHOT.pom [info] Main Scala API documentation to C:\Users\App\git\website2.0\target\scala- 2.10\api... [info] Compiling 57 Scala sources and 58 Java sources to C:\Users\App\git\websit e2.0\target\scala-2.10\classes... [error] C:\Users\App\git\website2.0\target

Is there any sample application that uses Play Framework 2.3 and Google App Engine? So far I have found this one: https://github.com/siderakis/playframework-appengine Here is another tutorial with example: http://viralpatel.net/blogs/first-play-framework-gae-siena-application-tutorial-example/ 来源： https://stackoverflow.com/questions/24069774/play-framework-2-3-and-gae-google-app-engine

using publishTo in build.sbt file, it can be automation the publishing progress . But asset files( in public folder) does not packaged. how to package and publish asset files? For locally publishing assets files , add this snippet in build.sbt file import play.PlayImport.PlayKeys._ packagedArtifacts in publishLocal := { val artifacts: Map[sbt.Artifact, java.io.File] = (packagedArtifacts in publishLocal).value val assets: java.io.File = (playPackageAssets in Compile).value artifacts + (Artifact(moduleName.value, "jar", "jar", "assets") -> assets) } Important notes in last function line: first

I am using the playframework (2.4) for Java and connecting it to Postgres. The play framework is being used as a restful service and all it is doing is insert,updates,reads and deletes using JDBC. On this play page https://www.playframework.com/documentation/2.3.x/JavaAsync it states clearly that JDBC is blocking and that play has few threads. For the people who know about this, how limiting could this be and is there some way I can work around this? My specific app can have a few hundred database calls per second. I will have all the hardware and extra servers but do not know how play can

In Play Framework 2.3, an action can produce a result from a successful future call like this: def index = Action.async { val futureInt = scala.concurrent.Future { intensiveComputation() } futureInt.map(i => Ok("Got result: " + i)) } But how can an action deal with a failed future call, i.e., a future that was completed by calling failure() instead of success() ? For instance, how could an action produce a InternalServerError result with the message returned in the future's failure's throwable? onComplete and onFailure callbacks don't seem to fit the action's flow (it needs to return a result,

I'm using slick to access database. I want to query like this: case class Coupon(couponId: Long, shopId: String) class Coupons(tag: Tag) extends Table[Coupon](tag, "coupons"){ def couponId = column[Long]("coupon_id") def shopId = column[String]("shop_id") override def * = (couponId, shopId) <> (Coupon.tupled, Coupon.unapply) } object Coupons extends TableQuery(new Coupons(_)){ def findCouponBy(couponId: Long, shopId: Option[String]) = { val s = DB.createSession() try { val q = for { coupon <- this.filter(c => c.couponId === couponId && shopId.map(s => c.shopId === s).getOrElse(true) } yield