• 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

File Repository

Jahia 6 was the first version to include the Java Content Repository as its standard file repository and build services on top of it. Actually, the integration of Jackrabbit is not a strong dependency, as Jahia uses the standard JCR API to offer access to multiple repositories. In Jahia 6 it was already possible to access CIFS/SMB file repositories, and a few other example implementations are also available (among these are FTP, Alfresco, Exo Platform, Nuxeo connectors). On top of the file repository services, different interfaces expose content through various interfaces such as WebDAV, template file browsing and Jahia’s AJAX UI. On the other side of the repository, integration with a rules engine is used among other things for image thumbnail generation and metadata extraction. This rule engine is also pluggable and can be extended by integrators to perform other specific logic upon repository events.Jahia 6 was the first version to include the Java Content Repository as its standard file repository and build services on top of it. Actually the integration of Jackrabbit is not a strong dependency, as Jahia uses the standard JCR API to offer access to multiple repositories. In Jahia 6 it was already possible to access CIFS/SMB file repositories, and a few other example implementations are available (among these are FTP, Alfresco, Exo Platform, Nuxeo connectors). On top of the file repository services, different interfaces expose content through various interfaces such as WebDAV, template file browsing and Jahia’s AJAX UI. On the other side of the repository, integration with a rules engine is used among other things for image thumbnail generation and metadata extraction. This rule engine is also pluggable and can be extended by integrators to perform other specific logic upon repository events.