[
https://jira.jboss.org/jira/browse/DNA-339?page=com.atlassian.jira.plugin...
]
Brian Carothers updated DNA-339:
--------------------------------
Attachment: DNA-339_RFC.patch
Attached an approximate solution for feedback. Salient features are:
- A JSR-283-like approach to type registration, currently only implemented in the
RepositoryNodeTypeManager
- Addition of a nodetypes package in the source directory that contains equivalent
versions of the registration-related interfaces that exist in JCR 2.0 and not JCR 1.0
- Partial validation implementation for type registration (maybe 75% right)
- Projection of types under the /jcr:system/jcr:nodeTypes node (not needed for
registration, but hard to isolate my changes at this point)
Missing features are:
- Type unregistration
- Full validation of types at registration time
- Extra validation required for type updating
- Proper internationalization of exceptions from type registration
- Logging
Potentially offensive features are:
- Refactor of findPropertyDefinition
- Thread-safety approach (partially implemented) for RepositoryTypeManager.nodeTypes
- Requirement that users order the types to be registered to eliminate forward references
Apologies for including the DNA-337 and DNA-338 fixes in this patch. By the time I got
this together, there was no good way to extricate them.
JCR Type Registration and Unregistration
----------------------------------------
Key: DNA-339
URL:
https://jira.jboss.org/jira/browse/DNA-339
Project: DNA
Issue Type: Feature Request
Components: JCR
Affects Versions: 0.4
Reporter: Brian Carothers
Attachments: DNA-339_RFC.patch
It would be useful for DNA to support type registration and unregistration (a la JSR 2.0
(draft) spec section 6.10).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira