-
Play!> framework design pattern #2 reviewed
In this post I write about a pattern to avoid code duplication for rendering the same objects (like combo boxes and so) in different views (a view to create an item or a view to edit existing ones). It has 2 things that couldn’t be done with the…
-
Play !> and 3-tier, n-tier architecture - Part II
In Part I, I introduced the use of Play! framework on 3-tier architecture. In this one, we will see how to use the native features of Play! to implement a 3-tier application. As we saw, the implementation of the Logic tier is easy with Play!. In this implementation, you can…
-
Play !> and 3-tier, n-tier architecture - Part I
Play!► is based on the MVC application model. This model, as named, is an application model, but in an enterprise ecosystem, you’ll have to integrate your application with the Information System, and apply 3-tier physical architecture, or n-tier architecture Figure 1. 3tier The 3-tier architecture The 3-tier architecture…
-
ubuntu 12.10 precise pangolin breaks my redmine and tomcat7 installation
My redmine installation was broken when I installed Precise pangolin. The home screen was ok, but I has errors when navigating on the app. I didn’t search much but found easyli the solution when I tried to install a package. I had errors when running sudo apt-get install…
-
Play!> & JSon : How-to select fields to expose (ExclusionStrategy)
Using JSON as data language to build an API for your Play application, the default behaviour is to render all fields of a class, and this recursively. This means render the fields of a Here a sample model example that could occurs in a bank application : A client is specified…
-
Play!> 2.0 Install it to /opt anyway
I don’t understand the new install of play!> framework 2.0 The documentation says : […]extract the archive to a location where you have both read and write access. (Running play writes some files to directories within the archive, so don’t install to /opt, /usr/…
-
Play!> framework How-To : binding @ManyToMany to views (without CRUD) and differents UI
This is a little How-To for binding @ManyToMany relationship in Play!> views. The model for this very simple : a Domain model , and a User model. Users can belong to many domains and domains can have many models. So, the Models are simple : @Entity public class Domain extends Model { public…
-
Play!> framework : binding checkbox to POJO
I’ve been quite a long time to find the good way to bind checkboxes in my views to boolean properties of my POJO. The only way I was able to handle the checkboxes was to pass explicitly the field to the save method of the controller and explicitly…
-
Play!> framework design pattern #2 : avoid code duplication to render same objects in differents views
If you have common code in your controllers to render objects in differents views, you’ll duplicate your code to instanciate your java objects in each method and pass them to the render method. The goal of this pattern is to avoid code duplication using the @Before/@After annotations…
-
Play!> framework design pattern #1
A bad pattern is to handle different code to manage edition of items and creation of new items in the forms. Typically you’ll pass an issue to the form when editing an existing one, and no one for the form to create new ones. Taking codeboard as an…