[dna-issues] [JBoss JIRA] Resolved: (DNA-302) Make JcrNodeTypeManager not dependent on JcrSession

[Randall Hauch (JIRA)]

     [ https://jira.jboss.org/jira/browse/DNA-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch resolved DNA-302.
-------------------------------

    Fix Version/s: 0.4
                       (was: 0.5)
       Resolution: Done
         Assignee: Randall Hauch


The patch resolved the issue.

> Make JcrNodeTypeManager not dependent on JcrSession
> ---------------------------------------------------
>
>                 Key: DNA-302
>                 URL: https://jira.jboss.org/jira/browse/DNA-302
>             Project: DNA
>          Issue Type: Sub-task
>          Components: API, JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>             Fix For: 0.4
>
>         Attachments: DNA-302.patch
>
>
> The JcrNodeTypeManager should not be dependent upon a JcrSession instance.  Most of the methods (including those in JcrNodeType, JcrNodeDefinition, and JcrPropertyDefinition) only need an ExecutionContext.  JcrNodeDefinition.getDefaultPrimaryType() seems to depend upon the NodeTypeManager to dynamically look up a type (there may be others).  This main mean that the JcrNodeTypeManager needs a method to allow adding types from a JcrNodeTypeSource (rather than a JcrNodeTypeSource be passed into the constructor).

-- 
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