The tree handler for the dms, was trying to load a HierarchyManager
class dynamically.
Yes and no. It was certainly not trying to load a HierarchyManager,
but possibly a tree handler class (AdminTreeMVCHandler) which most
likely depended on a HierarchyManager (through an import).
At least it was in version 1.1.
Looks like you've updated to 1.2 yesterday, and I haven't had time
to test it yet.
Will try to do it.
Only changed the pom.
Hum .. not too sure.
http://java.sun.com/j2se/1.4.2/docs/api/java/lang/
ClassNotFoundException.html
http://java.sun.com/j2se/1.4.2/docs/api/java/lang/
NoClassDefFoundError.html
*Error are in general thrown when the VM has a problem that can't be
recovered (well, yeah, some people try and recover from
OutOfMemoryExceptions, I know).
In this very case, I don'think it makes sense to try and let Magnolia
start if the HierarchyManager is not available :-D
WDYT ?
greg
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
