[ http://jira.magnolia.info/browse/MAGNOLIA-1345?page=comments#action_13407 ] Philipp Bracher commented on MAGNOLIA-1345: -------------------------------------------
In general: If a dipendency is optional the modul needs to handel the absence of the optional module properly. In this particular case I would advice to move the dms bootstrap files to an other place in the resources. The register methods should check the presence of the workspace and bootstrapp the files afterward. There are helper methods to implement this with ease. A hack (but a good one) would be to put the files into the path mgnl-boostrap/dms which means that the files are bootstrapped during the registration of the dms only. In case the dms is not present the files are completely ignored. > NPEs when a module tries to load content into a non existing repository > ----------------------------------------------------------------------- > > Key: MAGNOLIA-1345 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1345 > Project: Magnolia > Issue Type: Bug > Affects Versions: 3.0.1 > Reporter: Fabrizio Giustina > Assigned To: Fabrizio Giustina > Fix For: 3.1 > > > This happens when DMS is not installed on magnolia and the samples module is. > The samples module has not dependencies on DMS so it tries to load content > into the dms repository and a couple of NPE are thrown. In order to properly > fix this the samples module should be split making a samples-dms module > probably, but checking if a HierarchyManager is non null is absolutely needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
