|
OpenXava is a framework for developing business applications in an effective way. It allows rapid and easy developing of CRUD modules and report generation, but also it's flexible enough to develop complex real life business applications as accounting packages, customer relationship, invoicing, warehouse management, etc. OpenXava uses XML as definition language and Java as programming language. Currently OpenXava generates Java Web Applications (J2EE/Java EE), they 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 provides automatically the user interface, the data access, the Java code, the default behavior, etc. In this way, all common issues are solved easily, but always the developer has the possibility of programming manually any part of the application, in this way is flexible enough to solve the particular cases. OpenXava is based in the concept of 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.xml) is used, and all information about invoice concept (including data structure, user interface layout, mapping with database, validations, calculations, etc) is defined there. In a MVC framework the business logic (the Model]), the user interface (the View) and the behavior (the Controller) is defined separately. This type of frameworks are useful if the rate of changes for logic and data structure is low and the possibility of changing user interface technology or data access technology is high. In OpenXava for adding a new field to an Invoice the developer only needs to touch a single file: Invoice.xml But, the MVC frameworks are bad when the changes of structure and data is very frequent (as in the business application case). Imagine the simplest change, adding a new field to an Invoice, in an MVC framework, the developer must to change the user interface, the model class, the database table, moreover if the developer uses J2EE design patterns he has to change the DTO class, the Facade Session Bean, the Entity Bean mapping, etc. Another advantage of the business component frameworks is work distribution for teams. It's easy to do a business logic oriented distribution (Invoice for one developer, Delivery for other, etc), and not by technology layer (business logic for one developer, user interface for other, etc) Features These are some of the main features of OpenXava: See also | ||||||||
|
| |||||||||
 |
|
| |