• Technical Overview
  • Overview
    • What is Jahia?
    • The closer View
    • Technical Requirements
    • Everything is Content, whatever the type or source
      • Integrator and Developer Customization
    • Integrated technologies
    • Architecture Overview
    • Modules
    • Jahia's Different Actors
  • Web Layers
    • Content Flows
    • Templates and Views
    • The Jahia Template Studio
      • Page templates
      • Content Templates
    • REST API
      • Actions
      • Example : native iPhone/iPad application
    • Mobile Rendering
    • Macros
    • Filters
  • Back-end Layer
    • Workflow
    • JBoss Drools and event listeners
    • File Repository
    • Searching and Indexing
      • Full text queries using search tag librairies
      • Query Languages
    • Enterprise Jahia Tool - Authentication and Authorization
    • Import / Export
    • Enterprise Jahia Tool - Distant Server Publications
    • Portlets
      • Portlets vs. Modules
  • Enterprise Jahia Tool - Optimizing deployment and performance
  • Additional Resources

Architecture Overview

As you can see, the top layers are basic rendering and communication layers, while the underlying services are more modular. The blue boxes covered what is offered in the core services, either as core modules or framework, while the orange boxes show that modules may not only provide more content definitions, but also custom logic and much more.

Jahia 6.5 introduced modules to the architecture. Prior to this version, extensions to Jahia would be integrated through Spring beans being deployed, but no specific packaging was possible. Since 6.5, it is possible to package modules in WAR files that can then be deployed to extend or complement Jahia functionality. Actually a lot of default functionality in Jahia is built using modules, including, for example, the contribute mode or template sets.