Hi Simon, > java.lang.RuntimeException: error unmarshalling return; nested exception is: > > java.net.MalformedURLException: no protocol: de > at org.mmbase.bridge.RemoteContext.getCloudContext > (RemoteContext.java:50) > at org.mmbase.bridge.ContextProvider.getCloudContext > (ContextProvider.java:49) > at RMMCITest.main(RMMCITest.java:6) > Exception in thread "main"
Somehow your system ended up searching for a protocol named 'de' (like others that are 'http' and 'ftp') so - either the protocol 'de' is a protocol that's really needed and you somehow are lacking the protocol handlers (In that case it's probably a classloader or a classpath issue) I've had some problems with custom protocols when running inside a test system like JUnit. - or there's a 'problem' somewhere in your filenames or shomething. Does the string 'de' perhaps occur somewhere in a directory where your servlet engine is placed? Some googling indicates that putting spaces in your directory names is not a good idea. --- Fixed. As you pointed out, the problem was related to the spaces in the installation directory of Tomcat. I never use directory names with spaces for Java, but Tomcat 5 was an exception because it came with its own installer. To my surprise, Tomcat default installation doesn't work because of the default directory, isn't it? How can the Tomcat team distribute Tomcat 5 in such a manner?? Really astonished, Ignacio Renuncio.-
