Why to use OpenXava if we have Spring, Hibernate, JSF, EJB3 and so on?Nowadays we live great times. It's true that Spring, Hibernate, JSF and EJB3 are far better than J2EE 1.4. All these frameworks and technologies are good (in fact OpenXava uses some of them), but if you need to develop business application the amount of code to write continues being big, and the productivity is low comparing with other technologies (Visual Basic, 4GL, Delphi, RPG, etc). How scalable it is?OpenXava generates a standard Java EE/J2EE application, hence it's as scalable as Java EE/J2EE. What type of users manager system and navigation could you use with OpenXava?The modules generated by OpenXava are JSR-168 portlets, hence they are deployabled in any compliant Java Portal with its own security and navigation features. What Application Servers are supported?OpenXava has been tested with:
Any Servlet 2.3 compliant container can execute OpenXava applications. What Java Portals are supported?Any JSR-168 compatible portal. Although the next ones are tested:
What Development Tools can be used?The downloaded OpenXava zip file has a configured workspace to use with Eclipse. OpenXava is not using Eclipse resources but it's based in the Ant Tool (which it's open source). You can use whatever IDE that you want without problem or also from command lines. What JDK needs to run?The OpenXava works with JDK 1.4.2, JDK 5.0 and JDK 6.0. What licence type has OpenXava?LGPL. You can use OpenXava to develop every comercial project than you want. The unique forbidden thing is developing your own comercial version of OpenXava.
|