[OAK-493] Drop fallback in Node#getPrimaryType

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.6
• Assignee: Angela Schreiber
• Reporter: Angela Schreiber
• Created: 05/Dec/12 11:10
• Updated: 06/May/13 15:49
• Resolved: 05/Dec/12 14:58

Description

currently the implementation of NodeImpl#getPrimaryType has a fallback if the primary type
property is missing (to nt:unstructured). while that might have been useful in the beginning
when be basically didn't have anything running, i am not convinced that this is really
a reasonable setup for a mature implementation...

the regression i was referring to in OAK-490 wasn't caused by the move itself but by
the fact that i didn't (nor intend to) copy over that shortcut to the node type manager.

Issue Links

• relates to: OAK-124 Default to nt:unstructured for nodes where jcr:primaryType is not set