FAQ FAQ

How scalable is it?

OpenXava generates standard Java EE/J2EE applications, hence it's as scalable as Java EE/J2EE.
OpenXava uses JPA, Hibernate or EJB CMP2 (until v3.1.4) for persistence, and some session scope state at servlets level. The OpenXava code is good, but when you write your own code you must be wise in order to obtain a good performance, specially in batch processes, but this is an issue of Java EE not of OpenXava.

What type of user management system and navigation could you use with OpenXava?

OpenXava does not include a built-in user managament and navigation system. However, the applications generated by OpenXava are standard portlet applications, hence they are deployable in any compliant Java Portal (such as Liferay) with its own security and navigation features. Another option is to use NaviOX, an add-on for adding security and navigation to OpenXava applications.

What Application Servers are supported?

Any Servlet 2.4 compliant container can execute OpenXava applications. Versions previous to OX3.1 use Servlet 2.3.

If you want use EJB (optional in v2 or greater) you need at least a J2EE 1.3 application server.

What Java Portals are supported?

Any JSR-168/286 compatible portal.

What Development Tools can be used?

The OpenXava zip file has a preconfigured Eclipse workspace. However, OpenXava does not use any Eclipse specific resource but it's based in the Ant Tool (which it's open source), so you can use whatever IDE you want even a simple text editor and command line.

What JDK needs to run?

The OpenXava works with JDK 5.0, JDK 6.0 and JDK 7.0.
JDK 1.4.2 works fine with OpenXava 3.1.4 and JDK 1.3.1 works fine with OpenXava 1.2.1.

What browsers are supported?

OpenXava has been tested with:

  • Internet Explorer 9, 8, 7 and 6
  • Latest Firefox.
  • Latest Google Chrome.
  • Latest Safari.

What licence type has OpenXava?

LGPL. You can use OpenXava to develop any comercial project you want. The unique forbidden thing is to develop your own comercial version of OpenXava.