OpenXava is a framework to develop JavaEE/J2EE applications quickly and easily.
The underlying philosophy is to define with Java annotations or XML and to program with Java; the more definition and less programming the better.
The main goal is to build the most typical things in a business application easily, while still having the necessary flexibility to develop more advanced features as you require.
Below you can see some of the basic concepts of OpenXava.
Business component Business components are the fundamental pieces to create applications in OpenXava. In the OpenXava context, a business component is a Java class (although there also exists an XML version) that contains all the information about a business concept that you require to create applications. For example, all the information that the system needs to know about the concept of invoice is defined in the file Invoice.java.
In A Business Component You Can Define:
- The data structure.
- Validations, calculations and all logic associated with the business concept in general.
- The possible views of the component, i. e. the configuration of all possible user interfaces.
- The possibilities for the tabular data presentation. This is used in list mode (data navigation), reports, export to excel, etc.
- Object-relational mapping. This includes information about database tables and how to convert them to the objects of your Java application.
This way of splitting is good for working in groups, and allows you to develop generic business components for reuse in different projects.
Controllers A controller is a set of actions. An action is a button or link that a user can click on.
The controllers define the things that user can do with the business component in the application.These are specified in the file xava/controllers.xml of your project. In addition OpenXava has a set of predefined controllers in OpenXava/xava/default-controllers.xml.
The controllers are separated from the business components because one controller can be assigned to several business components. For example, a controller to make CRUD operations, to print in PDF format or to export to plain files, etc. can be used and reused for components like invoices, customers, suppliers, etc.
Application An OpenXava application is a set of modules. A module joins a business component with one or more controllers.
Each module of the application is what the end user uses, and generally it is configured as a portlet within a portal.
Project Structure A Typical Openxava Project Contains These Folders:
- [root]: In the root you can find build.xml (with the Ant task).
- src[source folder]: Contains your Java source code.
- xava: XML files to configure your OpenXava application. The main ones are application.xml and controllers.xml.
- i18n: Resource files with labels and messages in several languages.
- properties[source folder]: Property files to configure your application.
- data: Useful to hold the scripts to create the tables of your application, if needed.
- web: Web content. Usually JSP files, lib and classes. Most of the content is generated automatically, but you can put your own JSPs or other custom web resources here.
(65.7MB, Extension: ZIP)
Download alternate to OpenXava solution
Look at the free or trial alternatives and similar apps to OpenXava software by the tags. It's possible also to find substitutes for the most popular titles in the Software Development category.
Predicted future versions and notices:
The doDownload.com constantly monitors the update of all programs, including information from the OpenXava 5.0.2 changelog file, however sometimes it can happen that data are not complete or are outdated.We assume that author continue's to develop 5.1.0 version with further advanced features, and soon you will be informed. Equally important 6.0.0 upgrades of the program we will continue to monitor. Full OpenXava description has been compared with the overall software database and our algorithm has found the following applications (are showed below).