JPA (the Java Persistence API) sometimes does a little too much for its own good. Distinctions between managed and unmanaged entities or between save() and merge() are relevant when most objects stay in memory a long time, and are ‘synchronized’ with the database at different intervals during their lifetime.
In a Play! framework application, persistent data is rarely kept in memory for more than a single request. Hence an entity is going to be saved to the database almost after every time it is modfied. Because this is not the workflow JPA designers had in mind, sometimes JPA gets in the way.
After you have built the initial version of a web application, it can be hard to know what to add in version 2.0, tricky to know how add value and make it expensive software, and near-impossible to understand what features a web 2.0 application actually has. This article describes some common features that you might think are merely Nice To Have, and why you might really need them sooner rather than later.
Copyright © 2005-2012, Lunatech Research B.V. Tous droits réservés.