Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NodeType definitions are not fully JCR 2.0 compatible #62

Open
bergie opened this issue Nov 18, 2011 · 1 comment
Open

NodeType definitions are not fully JCR 2.0 compatible #62

bergie opened this issue Nov 18, 2011 · 1 comment
Assignees
@piotras

Comments

@bergie
Copy link
Member

bergie commented Nov 18, 2011

Currently the MgdSchemas for JCR built-in node types are a combination of JCR 1.x definitions and JCR 2.x definitions. They should be modified to fully conform to the JCR 2.x definitions.

This causes issues, like the current debate on mandatory properties of nt:resource.
@ghost ghost assigned piotras Nov 18, 2011
bergie added a commit to bergie/phpcr-midgard2 that referenced this issue Nov 18, 2011
@bergie
nt:address is a built-in type in JCR 2, refs midgardproject#62
ae8aeca
@bergie
Copy link
Member Author

bergie commented Dec 5, 2011

We should create a tool that builds MgdSchemas from the CND notation, and use the JackRabbit node definitions:
http://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-core/src/main/resources/org/apache/jackrabbit/core/nodetype/builtin_nodetypes.cnd

Note that a primary type should be marked as extending nt:base unless it extends another primary type.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@piotras piotras

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bergie @piotras