RegisterNodeTypeTask should also create root path
-------------------------------------------------

                 Key: MGNLDATA-150
                 URL: http://jira.magnolia-cms.com/browse/MGNLDATA-150
             Project: Magnolia Data Module
          Issue Type: Bug
    Affects Versions: 1.6.4
            Reporter: Jörg von Frantzius
            Assignee: Philipp Bärfuss


Our module has declared a module-dependency on the categorization module, and 
so we were assuming that the "/categorization" root path does exist already in 
the data repository when our custom {{ModuleVersionHandler}} is executed.

Unfortunately, for types registered with a {{RegisterNodeTypeTask}}, the 
rootpaths are created in the data repository only after versionhandlers have 
executed, namely during {{DataModule.start()}}. That's what the categorization 
module does.

This is usually a problem only on first server startup with an empty 
repository, which still creates irritation with our client when they startup 
our first application delivery. Also it takes some time to find out what the 
problem is, since we had a proper dependency on categorization module.

Would it be possible that {{RegisterNodeTypeTask}} also creates the necessary 
root path? DataModule.createRootPath() seems to be doing only:
{code}
ContentUtil.createPath(hm, rootPath, new ItemType(DataConsts.FOLDER_ITEMTYPE));
{code}

If {{RegisterNodeTypeTask}} can get access to the type definition, it should be 
able to do the same?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       


----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to