Just to document the real issue with rmi and spaces in paths so that when someone googles on the issue he/she will find the answer
The java.rmi.server.RMIClassLoader loads classes from network locations (one or more URLS) for marschalling and unmarschalling objects. The RMIClassLoader uses a codebase where to get the classes from. The codebase is a string with urls separated by spaces. I added this to the exception message in the RemoteContext class. I think that is the best place to document it. Nico ------------------------------------------------------ Document code? Why do you think they call it "code"? > -----Oorspronkelijk bericht----- > Van: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Namens Ignacio Renuncio > Verzonden: dinsdag 13 juli 2004 14:58 > Aan: [EMAIL PROTECTED] > Onderwerp: RE: Remote cloud connection error > > > > 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.- > >
