> >
> > Thanks Michiel for replying. It was my class-path. It was
> pointing to
> > an old mmbase.jar.
> >
> > Thanks again,
> >
> > _Curtney
> >
>
> Would it be a really weird idea to let mmbase print its path
> where it was loaded from on startup ?
>
> Daniel.
It is not so hard to do that. We could do something like this in
org.mmbase.module.core.MMBaseContext.initLogging()
log.info("mmbase.loadpath : " + getPathForClass(this.getClass().getName()));
/**
* The absolute pathname of the class file
* containing the specified class name, as prescribed
* by the current classpath.
*
* @param className Name of the class.
*/
public String getPathForClass(String className) {
if (!className.startsWith("/")) {
className = "/" + className;
}
className = className.replace('.', '/');
className = className + ".class";
java.net.URL classUrl =
this.getClass().getResource(className);
if (classUrl != null) {
return classUrl.getFile();
} else {
return null;
}
}
Now we know which mmbase.jar is loaded and that is the most important jar we
have.
Nico
-----------------------------------------------------------------------
A Supercomputer is a computer that runs an endless loop in two seconds.
