You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Tomas Pollak <to...@yahoo.com> on 2009/07/21 04:39:02 UTC
RMI call fails when URL contain spaces
Hello all,
I have this use case:
I'm developing a web applicaton that makes an RMI call to a server. If I have a standalone Tomcat instance, and deploy the war to it, it works fine.
However, when I use the maven-tomcat-plugin I get a MalformedURLException. Searching for this problem online there is some information like:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4496398
The problem's cause is that one or more jars from the classpath contain spaces in their path. This is indeed so, since all the maven dependencies are in the form: C:\Documents and Settings\user\.m2\.....
(The exception is: MalformedURLException: unkown protocol: and)
However there must be some bug with Tomcat (the maven plugin uses version 6.0.16), because when using the maven-jetty-plugin this problem doesn't occur.
If you debug and set a breakpoint in the method java.rmi.server.RMIClassLoader.newDefaultProviderInstance(), you'll notice that the spaces in the codebase URLs are not escaped, whereas with Jetty they are.
Could someone confirm if this is a bug, or if there is a workaround?
Cheers,
Tomás
Re: RMI call fails when URL contain spaces
Posted by André Warnier <aw...@ice-sa.com>.
And anyway, paths containing spaces are evil and should be proscribed.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: RMI call fails when URL contain spaces
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Tomas Pollak [mailto:tomas_pollak@yahoo.com]
> Subject: RMI call fails when URL contain spaces
>
> I'm developing a web applicaton that makes an RMI call to a server.
> If I have a standalone Tomcat instance, and deploy the war to it,
> it works fine.
>
> However there must be some bug with Tomcat (the maven plugin uses
> version 6.0.16), because when using the maven-jetty-plugin this
> problem doesn't occur.
So your webapp works properly under Tomcat, but not under the maven plugin, and somehow you conclude this is a Tomcat problem? The fact that the completely separate maven-Jetty plugin works has no relevance.
I would think you need to ask on a codehaus mailing list, since the maven plugin is not part of Tomcat nor even an Apache project.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org