OpenXava

OpenXava is a web framework for developing business applications in an effective way. It allows development of CRUD modules, report generation and business applications like accounting packages, customer relationship, invoicing, warehouse management, etc.

OpenXava
Stable release
6.1.2 / June 18, 2019 (2019-06-18)[1]
Written inJava
Operating systemCross-platform
Typeweb framework
LicenseGNU Lesser General Public License
Websiteopenxava.org

OpenXava allows developers to define applications with POJOs, JPA and Java 5 annotations.

Currently OpenXava generates Java web applications (Java EE) which can be deployed in any Java Portal Server (JSR168) as portlet applications.

The essence of OpenXava is that the developer defines instead of programming, and the framework automatically provides the user interface, the data access, the default behavior, etc. In this way, all common issues are solved easily, but the developer always has the possibility of manually programming any part of the application, in this way it is flexible enough to solve any particular cases. OpenXava is based on the concept of the business component.

Business component versus MVC

A business component includes all software artifacts needed to define a business concept. OpenXava is a business component framework because it allows defining all information about a business concept in a single place. For example, for defining the concept of Invoice, in OpenXava a single file (Invoice.java) is used, and all information about invoice concept (including data structure, user interface layout, mapping with database, validations, calculations, etc.) is defined there.

In an MVC framework the business logic (the Model), the user interface (the View) and the behavior (the Controller) are defined separately. These types of frameworks are useful if the rate of change of logic and data structures is low and the possibility of changing user interface technology or data access technology is high.

In OpenXava, the addition of a new field to an Invoice only requires changing a single file: Invoice.java. But MVC frameworks are cumbersome when changes to structure and data are very frequent (as in the business application case). Imagine the simplest change, adding a new field to an Invoice. In the MVC framework the developer must change three sections: the user interface, the model class and the database table. Moreover, if the developer uses Java EE design patterns he has to change the DTO class, the Facade Session Bean, the Entity Bean mapping, etc.

Using OpenXava makes it possible to allocate the development work using a business logic oriented task distribution. For example, Invoice to one developer, Delivery to another, as opposed to technology layer business logic to one developer, user interface to another.

gollark: Use a backslash to escape emojis.
gollark: The transactions are also a great way to get messages to admins and/or spam them.
gollark: Maybe there are more mining-specific emojis in Unicode?
gollark: ▲
gollark: They could use unicode arrows and unicode approximately-equal signs.

See also

References
  1. https://openxava.org/blog/xavapro-6.1.2-released

Can you pl. put the history of OpenXava including since when this framework exists

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.