Canigó (framework)

Uses your system voice; voice and rate in settings.

Snapshot

≈ 2 min read

Names in other languages

No names in other languages are held for this entry yet.

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

Canigó is the name chosen for the Java EE framework of the Generalitat de Catalunya.

Canigó is the name chosen for the Java EE framework of the Generalitat de Catalunya. ==Purpose and architecture== Canigó is defined as a "common technological framework for development and execution of web applications for corporative systems and departments of the Generalitat de Catalunya". It covers various functionalities: A common architecture for Java EE application building. Supplies a workspace, documentation, support and maintenance of its components. Simplifies the complexity inherent to Java EE, offering a referent framework. Offers a solution in keeping with the de facto standards all over the open source community. Offers an open solution that enables the possibility of adding and exchanging any piece of software with reduced costs. Offers an interconnectivity solution with the corporative services of the Generalitat de Catalunya. Canigó's architecture is based on Model–View–Controller. There is an abstraction process that allows the division of the application logics in three main components able to be developed by different roles of a team. Actually Canigó's architecture, as a MVC structured framework, is divided in 3 layers and 4 cross-cutting modules: Layers Presentation layer Business Logic layer Data Persistence/Integration layers Modules Framework Core Security modules Support module Operation module Canigó's a modular structure gives to developers the option to use only the needed modules to cover project requirements. Those modules are defined through interfaces, isolating them from chosen implementations. Canigó is based on a series resources, API's integration as JPA, and open source packages (Spring, Swagger, ...). It also offers extensions for those packages, adding a wide catalog of reusable components. One of the most important architectural basis is decoupling frontend and backend using REST API's. This architecture allows independent development teams to work on the frontend and backend. The framework consists of the blocks specified below: ==References== ==External links== Portal de Canigó

Text derived from https://en.wikipedia.org/w/index.php?oldid=1288458627 under CC BY-SA 4.0; modifications have been made.