You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2012/12/05 15:58:58 UTC

[jira] [Resolved] (OAK-493) Drop fallback in Node#getPrimaryType

     [ https://issues.apache.org/jira/browse/OAK-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela resolved OAK-493.
------------------------

    Resolution: Fixed
    
> Drop fallback in Node#getPrimaryType
> ------------------------------------
>
>                 Key: OAK-493
>                 URL: https://issues.apache.org/jira/browse/OAK-493
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>            Reporter: angela
>            Assignee: angela
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira