OpenXava 3.1 is a framework to develop Java Enterprise applications in a different way: OpenXava avoids MVC. You provide only your POJOs annotated with JPA and you obtain an application ready for production. With OpenXava, you only need to write your model, POJOs and Java 5 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 Excel, searching, sorting, validations etc. You only need to write a simple Java class, no XMLs, no JSPs and no code generation. Look at the demos. The main new feature of 3.1 is that generates AJAX appplications, in this way if you update to OX3.1, your OX (3.x, 2.x, or 1.x) applications will be AJAX without touching a single line of code. In the other hand, if you application is not OX but you use JPA entities, you can move your JPA code to an OpenXava application and obtain an AJAX portal application easily. OpenXava is not only for writing simple CRUDs for simple classes, you can create sophisticated applications with complex logic and advanced UI. OpenXava supports references, collections, inheritance, nested tabs, nested frames for grouping, etc. If you develop business applications, use JPA or are interested in Java Portals (as Liferay, WebSphere Portal or JetSpeed) do not doubt, download OpenXava and evaluate it. OpenXava is LGPL so you can develop commercial applications with it. More info: http://www.openxava.org/ What do you think about this way to develop applications? Do you think that MVC frameworks (SpringMVC, JBoss Seam, RubyOnRails or Grails) are as productive as VisualBasic, 4GLs, RPG, etc. for business applications? Do you think that MVC is always the best solution?
- Posted by: Javier Paniza
- Posted on: December 19 2008 07:47 EST
- Integrating with more mature frameworks? by Casey Butterworth on December 20 2008 09:06 EST
- Re: OpenXava 3.1 released: Increase productivity avoiding MVC by Thai Dang Vu on December 21 2008 05:02 EST
- Re: OpenXava 3.1 released: Increase productivity avoiding MVC by Javier Paniza on December 22 2008 04:20 EST
- Re: hikaye by Stephane Vaucher on December 21 2008 23:06 EST
- Comparison to Naked Objects by Douglass Parker on January 01 2009 14:12 EST
I don't know if I'd base an entire application around this, but the demos are pretty cool and I think this would be a useful toolkit in addition to a more comprehensive web framework. I didn't read any of the user guides, but has any thought been given to providing hooks into other frameworks so that developers can use this for CRUD features while still being able to use their web framework of choice?
thought been given to providing hooks into other frameworks so that developers can use this for CRUD features while still being able to use their web framework of choice?Yes. It's possible integrating OX with other frameworks. At end of the day an OX application is a standard Java Web Application. so you can extend it and mix with your favourite framework. Also it's useful that OX allows you put in any part your own handmade user interface. Look at customization doc. I personally think that the better way for integration is using Java Portals (as Liferay or WebSphere Portal). Thus you can have two or three applications developed with different frameworks and languages, however from the user viewpoint there are only one, with the same look & feel and user management. In this way, you can even integrate an OpenXava application with a RPG one (using IBM WebFacing) Cheers
With OpenXava, you only need to write your model, POJOs and Java 5 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 Excel, searching, sorting, validations etc. You only need to write a simple Java class, no XMLs, no JSPs and no code generation.Maybe I'm wrong, but can that be done with Seam? And if you have time to learn Seam, you can extend your application.
but can that be done with Seam?With Seam you must develop your UI using JSF (or another presentation technology). OX produces automatically, and on the fly, the user interfaces instead. OpenXava does not use scalfolding or passive code generation. You never need to touch the generated code because generated code does not exist. You only work with your POJOs and annotations. There are other model-driven frameworks like OX, but Seam is not one of them. You can combine Seam with OX. OX supports JPA, Hibernate Annotations and Hibernate Validator. So, a Seam application and an OpenXava application has a lot of code in common. Combining, or migrating from one to other is easy. Cheers
Can't an editor/admin ban this spammer instead of removing a few of his posts?
What is the difference between this and Naked Objects?