This article tries to demonstrate that Java can be more productive than Ruby.
We are going to develop the same application of the article Rolling with Ruby
on Rails Revisited (part 1 [1] and part 2 [2]) but using POJO [3]s annotated
with JPA [4] and a Model Driven Framework, OpenXava [5] in this case. The
result is that with less code, and less time you obtain a more powerful
application.
Ruby and rails: The regressive framework
Ruby on rails [6] is so elegant, so easy, so productive. I cannot avoid read
and heard continuously these comments. For example, the article Rolling with
Ruby on Rails Revisited of Bill Walton says:
“What would you think if I told you that you can develop a web application
at least ten times faster with Rails than you can with a typical Java
fra... (more)
OpenXava 3.1.4 is an open source framework to rapid development of Portlet
Enterprise applications deployable in WebSphere Portal 6.1.
With OpenXava, you only need to write your model, POJOs and Java annotations.
You do not need to write the view, and the controller (for CRUD, printing,
etc) is reused. And from that you'll have an application for CRUD, report
generation in PDF, export to ... (more)
OpenXava 3.1.2, released recently, is a model-driven framework to develop
Java Enterprise applications in an agile way: With OpenXava you provide only
your POJOs annotated with JPA and you obtain an AJAX application ready for
production.
The main new feature of this 3.1.2 release is the support for view
inheritance. Although OpenXava generates a workable user interface from your
naked JP... (more)
OpenXava 3.1.3 is a framework to develop Java Enterprise applications in a
different way: OpenXava avoids MVC. It's a JPA Application Engine in that you
provide only your POJOs annotated with JPA and you obtain an application
ready for production.
Productivity
With OpenXava, you only need to write your model, POJOs with annotations. You
do not need to write the view, and the controller (f... (more)
This is a story about creating a user interface easily, or better yet, about
having good user interfaces without working for them.
The Problem
Once upon a time, you created a really cool invoicing application. Your
wonderful application had an agile MS-DOS (or Unix, or AS/400, or HOST)
character interface, but your users demanded a Windows interface: more
beautiful, and easier to use. So,... (more)