|This article is an orphan, as no other articles link to it. Please introduce links to this page from ; try the Find link tool for suggestions. (February 2009)|
2.0 / November 4, 2008
The J2EE standard includes Servlet and JSP specifications for Web applications. Although these specifications provide the basic infrastructure for creating Web applications, they do not establish the application design.
Creating the application execution architecture goes beyond creating a collection of common application services, such as data access, e-mail delivery or queue management objects. It must provide the base architecture for the applications, defining the tier structure and design templates used in each of them.
The best practices and design templates that have come out of the Java community facilitate the creation of quality application architectures on which to develop the applications. However, developing an application architecture from scratch, based on templates, is costly, repetitive and more open to errors that starting with an existing one.
It uses a model-view-controller model.
The development framework is designed taking into account the need to constantly upgrade and adapt a platform of this type. The openFrame development team, together with the clients where it is implemented, is currently upgrading this technology in order to improve:
- The productivity of developments with plugins or tools designed specifically to support development
- The quality of the software, with the inclusion of code quality management (JUnit, Apache JMeter, Maven) and continuous integration (Cruise Control) methodologies
- The management and reuse of projects and components (openForge, CVS)
New release 2.0
OpenTrends released openFrame 2.0. (see news)