Details
-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
None
Description
Although we would not migrate to jcr2/jackrabbit2 soon, it would be nice to make ProviderImpl compatible so that we could start "experimenting" a migration.
Jackrabbit 2.0 seems to work fine as a drop-in replacement for older version, with only a few required changes to the nodetype registration:
- the ProviderImpl class have to be modified since the return value of NodeTypeReader.read() has been changed from NodeTypeDef[] to QNodeTypeDefinition[]
- the nodetype definition for mgnl:resource contains a primaryItemName="jcr:data" property which is not needed (since it already extends nt:resource) and that is not allowed in 2.0
ProviderImpl could be easily be updated to support both jackrabbit versions by using reflection. The change for supporting jackrabbit 2 is really small.
Checklists
Acceptance criteria
Attachments
Issue Links
- is related to
-
MAGNOLIA-3985 primaryItemType set on mgnl:resource (in custom_nodetypes.xml) prevents application from being able to start up repo
-
- Closed
-
-
MGNLBACKUP-27 Jackrabbit 2.0 compatibility
-
- Closed
-