Openbravo in English

Runtime Environment

To run the code, the application must be installed in a server running MVC Framework Foundation (which provides support for the MVC) and a group of third-party applications that we call the operating environment. Users need nothing more than a standard Web browser.

The WAD and the MVC-FF are largely Openbravo's internal development. The model data dictionary is an extension of the Compiere with the original modules (such as production), and the necessary adjustments to adapt to European and Spanish accounting standards and payment processes.

Openbravo: Operating Environment

Openbravo requires a well-known third-party applications such as Tomcat, Ant, Log4j, and some other utilities. Oracle Database 10g (release 2 SE) or PostgreSQL is also required.

The model is based on standard SQL, so it is not necessary to use an EJB server. We use Apache Tomcat as the servlet container, but others may be used instead.

Ant is used to make construction and Log4j is used for debugging purposes. All these applications can be installed on either Linux or Windows.

MVC Foundation Framework (MVC-FF)

MVC-FF is composed of a set of utilities developed by Openbravo: XmlEngine, and SQLC HttpBaseSecureServlet. MVC-FF is necessary to enable the development files for Decoupled Model, View, Control components of the MVC architecture.

Cet ensemble de services d'utilité publique a été utilisée dans le développement de nombreuses autres applications MVC, et il s'est avéré très efficace pour l'équipe de développement Openbravo

XmlEngine

XmlEngine is a utility used to create XML / HTML from a template in XML / HTML and an XML configuration file containing the dynamic data to insert into the model. XmlEngine is easy to use because the design of the model is identical to the desired outcome. Data entry is found in places where the data will be displayed using the XML / HTML attributes like "id" or tags like "div". The configuration file maps the fields from the data source with the locations identified in the model. To improve performance, the models are read and stored in memory. When a page is needed, the model creates a document that fills with data supplied by the application. With this tool, we generate forms to edit a file, a list of selected files, create reports with grouping levels or print specific forms of implementation.

SQLC

SQLC (SQL compiler) is a utility used to avoid repetition of the task of writing Java classes to interact with the database. The input is an XML file that contains the SQL standard and the parameters used in the statements. SQLC reads this file and generates a Java class that has all the necessary code to connect to the database, run the application, read a record and create standard Java return types for these methods.

HttpBaseServlet

HttpBaseServlet HttpBaseSecureServlet are servlets and from which all servers in the control system that implement the component of MVC are derived. These servlets implement features such as authentication, authorization, database connectivity and error handling. Servlets are derived from HttpBaseSecureServlet control reading data, interacting with the database with classes generated by SQLC and exit with XmlEngine.

Data Model Dictionary and WAD

Automation of code generation is obtained using the data model dictionary and the WAD (Wizard for Application Development). WAD automatically generates all the files the application with an MVC architecture. The files that are generated using XmlEngine, and SQLC HttpBaseSecureServlet.

Automation of code generation provides a better quality because the files are encoded using the same rules and style. The domain knowledge is contained by the model and not in code written manually. Thus, improving functionality implemented over time in WAD are added to all files when the code is regenerated without any additional intervention.