playframework-2.2

From what I can see in the auto-generated application.conf file, dates/times in Play Framework 2.2 are formatted according to the definition of date.format in that file. I have, for instance, defined date.format=yyyy-MM-dd date.format.dk=d. MMMM yyyy These values, however, seem to be ignored by the framework when printing dates in Scala templates. This thread gives a solution where one enters the pattern directly into the template as myDate.format("yyyy-MM-dd") . (If using Jodatime I guess this becomes myDate.toDate().format("yyyy-MM-dd") since there is no format() defined on the DateTime

For this example, lets assume the user would like to update just the first name of his online profile. Form: <form data-ng-submit="updateFirstName()"> <label for="firstName">First name<label> <input type="text" name="title" data-ng-model="firstName"> <button type="submit">Update first name</button> </form> Controller: public class UsersController { public static Result updateFirstName() { Form<User> filledForm = Form.form(User.class).bindFromRequest(); // TODO: Validate firstName // if hasErrors() return bad request with errors as json // else save and return ok() } } Model: @Entity public

I am building a web application with PLAY framework 2.2.1 and am trying to display all available http get query parameters for the requested site in the address bar, even the ones that are not set in the request. In cases where not all http get parameters are set, I want to add the unset parameters with the default values and make a redirect. I have a site that can be requested with GET: GET /test controllers.Application.test(q:String, w:String ?= null, f:String ?= null, o:String ?= null) Here is the method that I'd like to have in controllers.Application : public static Result test(String q,

I am getting the following error when running my Play Framework 2.2.x (Java) project: Configuration error Cannot register class [models.SomeClass] in Ebean server The error messages displayed in the browser points me to the line ebean.default="models.*" in my application.conf , and the console tells me that I have a java.lang.VerifyError: Bad type on operand stack in one of my methods. There is nothing special about the methods for which this happens, and it has happened for a handfull of methods now. I have found out that the error can be avoided by using a static method instead: that is by

Lets say I have these tables: ORDER: id ITEM: id ORDER_ITEM: order_id, item_id The table: ORDER_ITEM is a bridge table between ORDER and ITEM . How do I describe this threesome to Ebean ? I would prefer not to use raw SQL so that I can still create and update these entities. UPDATE Sat Nov 9 02:32:40 UTC 2013 Ok, lets make this problem harder and more representative of my actual situation. The column names dont fit the convention: ORDER: order_number ITEM: item_number ORDER_ITEM: my_order, my_item You don't have to create special bridge table yourself unless you want to have other fields there

I have my custom authenticated action that is like def Authenticated(rights: String*) = new ActionBuilder[MyAuthenticatedRequest] { *** } In my controller I use this action to check the user has the right to view the page def password = Authenticated(UserRights.USER) { implicit request: MyAuthenticatedRequest[_] => Users.findById(request.account.id) match { case Some(user) => Ok(views.html.settings.password(frontUser, user)) case _ => NotFound } } My oject Users uses slick to retrieve the user in the database def findById(id: Long)(implicit s: Session): Option[User] = users.where(_.id === id)