[ http://jira.magnolia.info/browse/MAGNOLIA-762?page=comments#action_11768 ]
Philipp Bracher commented on MAGNOLIA-762: ------------------------------------------ a virtual uri mappping will solve the issue > MgnlContext not initialized if a jsp is called directly (leads to javascript > exception 'importClass not defined') > ----------------------------------------------------------------------------------------------------------------- > > Key: MAGNOLIA-762 > URL: http://jira.magnolia.info/browse/MAGNOLIA-762 > Project: magnolia > Type: Bug > Reporter: Philipp Bracher > Assignee: Philipp Bracher > Fix For: 3.0 RC1 > > > If one opens the admin central one get's sometimes the javascript message: > not defined importClass() .. > caused by > java.lang.NullPointerException > at > info.magnolia.cms.beans.runtime.MgnlContext.getLocale(MgnlContext.java:97) > at > info.magnolia.cms.i18n.MessagesManager.getMessages(MessagesManager.java:270) > at > org.apache.jsp.admintemplates.js.admincentral_jsp._jspService(admincentral_jsp.java:262) > This happens because the jsp does not initialize the context. Should we > create a filter which sets the context if a jsp is called directly? > Currently it works only because tomcat reuses the thread ;-) -- 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 ----------------------------------------------------------------
