There should be more info in either the magnolia or tomcat logs for this
immediately following "Unable to compile class for JSP".
On the outside guess, I've heard of instances where problems occur in
tomcat's work directory -- files get locked, flagged read-only, etc.,
.... You could try stopping tomcat, clearing the work directory, and
then restarting. This doesn't harm anything although you will
experience a small delay as jsps are recompiled on first request.
--David
Ben Brock wrote:
I've installed Magnolia 2.1.5 a number of times successfully, but can't
get by this error now. Has anyone seen it before?
ERROR
org.apache.jackrabbit.core.nodetype.virtual.VirtualNodeTypeStateManager
04.10.2006 17:50:21 -- Unable to index new nodetype:
javax.jcr.ItemNotFoundException
ERROR info.magnolia.cms.servlets.EntryServlet 04.10.2006 17:51:23 --
Failed to forward - /admintemplates/adminCentral/adminCentral.jsp
ERROR info.magnolia.cms.servlets.EntryServlet 04.10.2006 17:51:23 --
Unable to compile class for JSP
Thanks in advance,
Ben Brock
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
