jahia-java-jcr

Codify Jahia JCR best practices for sessions, workspaces, nodes, and mixins.

Updated Mar 10, 2026

Search Tags:#workspace #session #locking #node-operations #jcr #jahia

Ready to run

npx skills add https://github.com/Jahia/formidable --skill jahia-java-jcr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jahia-java-jcr
Source: https://github.com/Jahia/formidable/tree/main/.agents/skills/jahia-java-jcr
Command: npx skills add https://github.com/Jahia/formidable --skill jahia-java-jcr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jahia Java developers often mis-handle the JCR lifecycle, workspace boundaries, and node operations, leading to data loss, security gaps, or concurrency bugs.

Core Features & Use Cases

Correct session and workspace usage patterns for read/write operations.
Safe mixin handling, versioning, and locking practices to prevent data loss and conflicts.
Practical pitfalls to avoid, with guidance for code review and implementation.

Quick Start

Refer to this guide when implementing or reviewing Jahia Java code that reads or writes the JCR to ensure correct sessions, workspaces, and locking.

Frequently Asked Questions about jahia-java-jcr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I handle Jahia JCR sessions and workspaces correctly for read and write operations?▼

Correct Jahia JCR session and workspace usage requires selecting the right session for read operations versus write operations, ensuring workspace boundaries are respected to prevent data loss and concurrency bugs.

What is the safest way to manage JCR node locking and versioning in Jahia Java modules?▼

Safe JCR node locking and versioning in Jahia involves applying codified best practices for mixins and robust error handling, preventing data conflicts and ensuring safe concurrent access during backend module development.

Why does my Jahia JCR code lose data or cause security gaps during node operations?▼

Jahia JCR code loses data or creates security gaps when developers mis-handle the JCR lifecycle, workspace boundaries, or node operations, which requires applying correct session selection and node name handling patterns.

Can I use this guide for Jahia code reviews involving ACLs and mixin handling?▼

Yes, you can use this guide during Jahia code reviews to verify correct ACLs, safe mixin handling, and proper workspace routing, ensuring backend Java modules follow robust JCR error handling practices.

What are the common JCR pitfalls to avoid when implementing Jahia backend Java modules?▼

Common Jahia JCR pitfalls include incorrect session selection, improper workspace routing, and poor node name handling, which are addressed by applying robust error handling and correct lifecycle management practices.

Do I need specific Jahia JCR patterns for safe data access in backend module development?▼

You need specific Jahia JCR patterns for safe data access to ensure correct session selection, workspace routing, and node operations, preventing data loss and concurrency bugs during backend Java module development.