Indeed for people who already use Hibernate to derive their persistence layer from a POJO domain model, Naked Objects can be thought of as performing the same function but upwards to the presentation layer.
Indeed for people who already use Hibernate to derive their persistence layer from a POJO domain model, Naked Objects can be thought of as performing the same function but upwards to the presentation layer.Tags: Halimbawa Ng ThesisBest Experience In Life EssayMy Mother Essay For Class 4Creative Writing Lesson Ideas Ks4Monthly Book Report ThemesPolitical Ideology Essay Liberal
Going back to touch on Constantine's point about the UI being vital; end users these days are not expecting a good UI as apposed to a good functionally sound domain implementation, or even vice versa - they want both.
The Naked Objects architectural pattern is well suited for rapid prototyping.
For those not familiar with earlier versions, Naked Objects is an open-source Java-based framework that takes a POJO domain object model and turns it into a complete, executable application.
It auto-creates a user interface that is a direct reflection of the domain model, offering the option of either a rich-client interface or a pure HTML interface as shown below (you can view both on our online demonstration application); and it auto-creates a persistence layer using Hibernate.
As a software engineer that is the most difficult thing to get correct, and is the thing that is most likely to make or break the success of your project/app.
UI Designers of course argue different, arguing that a good UI is critical and fundamental to a successful application (it is this stick that Larry Constantine beat the Naked Objects concept with some time back.The advantage is that Naked Objects both requires and facilitates the specification of very pure domain object models - and this results both in higher agility (ease with which future changes in requirements can be accommodated) and also in far greater levels of re-use.At the DSFA in Ireland, where we have implemented a set of large scale mission-critical applications using Naked Objects (2.0), we aimed for 90% re-use of the business code between applications; for one significant new application we achieved 98% (meaning that we replaced an application that had 50,000 lines of bespoke business code with one that contained @Member order tells Naked Objects where the Email Address field should be rendered in relation to other fields.I am not entirely unsympathetic to their stance and I certainly think a good UI helps, but without a sound domain model a fancy UI is worthless.The same cannot be argued for the reverse (I know since I've developed a few such apps, a good few of which were deemed a success and are still in operation today).AJAX is another obvious direction, and we know that Dave Crane, author of the best-selling ' Ajax in Action' book has been experimenting with Naked Objects.There is an obvious synergy between Naked Objects and Hibernate.Interestingly, Pawson has recounted how Trygve Reenskaug himself had stated that the Naked Objects pattern was the ultimate end game to his Model-View-Controller pattern.This certainly gives weight and validity to Naked Objects as an architectural pattern (in the West of Scotland we call this "hawners"). The Naked Objects MVC framework is interesting from a number of points of view: As a final observation Pawson claims that Naked Objects works well for sovereign applications but it does not lend itself very well to transient applications.Using the pattern, you only need to write the domain objects, everything else is autogenerated by the framework.We are pleased to announce, today, the release of Naked Objects 3.0.