[JCR-1096] Problems with custom nodes in journal

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.1, 1.2.2, 1.2.3, 1.3, 1.3.1
• Fix Version/s: 1.3.3
• Component/s: clustering
• Assignee: Dominique Pfister
• Reporter: Raffaele Sena
• Created: 29/Aug/07 01:09
• Updated: 08/Oct/07 10:47
• Resolved: 31/Aug/07 07:52

Description

I have an application that uses custom node types and I am having problems in a clustered configuration.

Issue 1: the following definition in a nodetype is incorrectly read from the journal:
+ * (nt:hierarchyNode) version

The * is stored in the journal as x002a since it should be a QName and it gets escaped.
When read, the code ...core.nodetype.compact.CompactNodeTypeDefReader.doChildNodeDefinition does the following test:

if (currentTokenEquals('*'))

{ ndi.setName(ItemDef.ANY_NAME); }

else

{ ndi.setName(toQName(currentToken)); }

Since currentToken is x002a and not * toQName(currentToken) is called but it fails.
I changed the test to:
if (currentTokenEquals('*') || currentTokenEquals("x002a"))
....
and that fixes the problem.

Issue 2: when storing a nodeType in the journal the superclass nt:base is not store, but when reading I get an error saying the node should be a subclass of nt:base.

The code in...core.nodetype.compact.CompactNodeTypeDefWriter.writeSupertypes skips nt:base when writing the node.

When reading the nodetype definition from the journal the following exception is thrown:

Unable to deliver node type operation: [

{http://namespace/app/repository/1.0}

resource] all primary node types except nt:base itself must be (directly or indirectly) derived from nt:base

probably because nt:base is not re-added to the nodetype definition