| french | english |
 |
|
| Sign in | |
| 02-10-07 / 20:53 : Naked Objects 3 : like WebObjects/DirectToWeb ? (cjed) |
| TSS provides an article about Naked Objects 3.0, a new framework that allows applications generation (rich client or flat HTML) from an object model. The announced particularity is that it doesn't use a controller object contrary to MVC frameworks (Struts, etc.) Actions are triggered directly and only on model objects (POJO). Well, it is funny, as it is presented as revolutionnary. And what about WebObject and its DirectToWeb generator ? It has been here from close to 15 years. And WO is far more rich (real components framework with a large UI components library that has been tested from a decade, and whose concepts inspired Tapestry) ! We can even read in this interesting interview at JSFCentral about Exadel/Ajax4JSF an honnest answer : M: Some would argue that WebObjects, Tapestry, and ASP.NET introduced component-oriented web development first. Do you think JSF offers anything different than these frameworks? MK: I wouldn't argue otherwise. I believe JSF builds on a lot of features from these frameworks such as component web development and Tapestry-like features with the Facelets extension. There are a few areas where JSF provides even more. For example, it's an open standard, which is very important Then WO would have had a sole problem, it wasn't standard. Well, neither Struts nor Hibernate followed specs at start (there is now JPA for Hibernate, in fact JPA spec took ideas from Hibernate...), they grew to de facto strandard... JSF also hides the controller, POJO attributes and methods are referenced directly in the JSF tags attributes (objects are injected through IOC). Then these two frameworks yet hide HTTP (they generate particular links when tags rendering occurs, in order to persist the components model on the server. In .NET it is somewhat the same, with a huge encoded string/HTTP parameter that drives the WebForms components state). |
| Comments |
| Write a comment |