[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22411#action_22411
 ] 

Grégory Joseph edited comment on MAGNOLIA-2711 at 5/5/09 5:10 PM:
------------------------------------------------------------------

Is this what you had ?
{noformat}
2009-05-05 15:41:22,223 ERROR 
.[localhost].[/magnolia-empty-webapp-4.1-SNAPSHOT]: Exception sending context 
initialized
___ event to listener instance of class 
info.magnolia.cms.servlets.MgnlServletContextListener
java.lang.IllegalStateException: Can't instantiate an implementation of this 
class 
___ [info.magnolia.imaging.filters.text.TextOverlayImageFilter]: 
InstantiationException: 
        at info.magnolia.cms.util.FactoryUtil.newInstance(FactoryUtil.java:124)
        at 
info.magnolia.content2bean.impl.Content2BeanTransformerImpl.newBeanInstance(Content2BeanTransformerImpl.java:325)
        at 
info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toBean(Content2BeanProcessorImpl.java:103)
        at 
info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toMap(Content2BeanProcessorImpl.java:173)
        at 
info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toBean(Content2BeanProcessorImpl.java:101)
        at 
info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toMap(Content2BeanProcessorImpl.java:173)
        at 
info.magnolia.content2bean.impl.Content2BeanProcessorImpl.setProperties(Content2BeanProcessorImpl.java:140)
        at 
info.magnolia.content2bean.Content2BeanUtil.setProperties(Content2BeanUtil.java:204)
        at 
info.magnolia.content2bean.Content2BeanUtil.setProperties(Content2BeanUtil.java:194)
        at 
info.magnolia.module.ModuleManagerImpl.populateModuleInstance(ModuleManagerImpl.java:387)
        at 
info.magnolia.module.ModuleManagerImpl.startModules(ModuleManagerImpl.java:312)
        at 
info.magnolia.module.ui.ModuleManagerWebUI.onStartup(ModuleManagerWebUI.java:80)
        at 
info.magnolia.cms.beans.config.ConfigLoader.load(ConfigLoader.java:108)
        at 
info.magnolia.cms.servlets.MgnlServletContextListener$2.exec(MgnlServletContextListener.java:177)
        at 
info.magnolia.context.MgnlContext.doInSystemContext(MgnlContext.java:377)
        at 
info.magnolia.cms.servlets.MgnlServletContextListener.startServer(MgnlServletContextListener.java:175)
        at 
info.magnolia.cms.servlets.MgnlServletContextListener.contextInitialized(MgnlServletContextListener.java:171)
{noformat}

This just happened to me while restarting an instance that add a module's 
configuration referring to a class i renamed (and/or made abstract) while 
developing.

The 404 is "only" a side effect of the whole app not being started at all.
With MAGNOLIA-1670, we could maybe introduce a way to "disable" modules when 
their loading fails.¨

This one is probably happening since we fixed MAGNOLIA-2552; which is fine, but 
really calls for MAGNOLIA-1670 to be taken care of too.

      was (Author: gjoseph):
    Is this what you had ?
{noformat}
2009-05-05 15:41:22,223 ERROR 
.[localhost].[/magnolia-empty-webapp-4.1-SNAPSHOT]: Exception sending context 
initialized event to listener instance of class 
info.magnolia.cms.servlets.MgnlServletContextListener
java.lang.IllegalStateException: Can't instantiate an implementation of this 
class [info.magnolia.imaging.filters.text.TextOverlayImageFilter]: 
InstantiationException: 
        at info.magnolia.cms.util.FactoryUtil.newInstance(FactoryUtil.java:124)
        at 
info.magnolia.content2bean.impl.Content2BeanTransformerImpl.newBeanInstance(Content2BeanTransformerImpl.java:325)
        at 
info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toBean(Content2BeanProcessorImpl.java:103)
        at 
info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toMap(Content2BeanProcessorImpl.java:173)
        at 
info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toBean(Content2BeanProcessorImpl.java:101)
        at 
info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toMap(Content2BeanProcessorImpl.java:173)
        at 
info.magnolia.content2bean.impl.Content2BeanProcessorImpl.setProperties(Content2BeanProcessorImpl.java:140)
        at 
info.magnolia.content2bean.Content2BeanUtil.setProperties(Content2BeanUtil.java:204)
        at 
info.magnolia.content2bean.Content2BeanUtil.setProperties(Content2BeanUtil.java:194)
        at 
info.magnolia.module.ModuleManagerImpl.populateModuleInstance(ModuleManagerImpl.java:387)
        at 
info.magnolia.module.ModuleManagerImpl.startModules(ModuleManagerImpl.java:312)
        at 
info.magnolia.module.ui.ModuleManagerWebUI.onStartup(ModuleManagerWebUI.java:80)
        at 
info.magnolia.cms.beans.config.ConfigLoader.load(ConfigLoader.java:108)
        at 
info.magnolia.cms.servlets.MgnlServletContextListener$2.exec(MgnlServletContextListener.java:177)
        at 
info.magnolia.context.MgnlContext.doInSystemContext(MgnlContext.java:377)
        at 
info.magnolia.cms.servlets.MgnlServletContextListener.startServer(MgnlServletContextListener.java:175)
        at 
info.magnolia.cms.servlets.MgnlServletContextListener.contextInitialized(MgnlServletContextListener.java:171)
{noformat}

This just happened to me while restarting an instance that add a module's 
configuration referring to a class i renamed (and/or made abstract) while 
developing.

The 404 is "only" a side effect of the whole app not being started at all.
With MAGNOLIA-1670, we could maybe introduce a way to "disable" modules when 
their loading fails.
  
> Failure to resolve class when finishing installation leads to 404 page being 
> displayed after installation
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: MAGNOLIA-2711
>                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2711
>             Project: Magnolia
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Jan Haderka
>            Assignee: Boris Kraft
>
> Stacktrace attached. Hitting the back button and clicking on "Start Magnolia" 
> button again leads to admin interface being displayed (on author) as 
> expected. The exception in UI appears most likely because initialization is 
> not finished yet. We should either postpone those or make sure some better 
> page is displayed then default tomcat's 404.

-- 
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/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to