Bug 49739 - Problem with setting baseURL if there's a space in the path name
Summary: Problem with setting baseURL if there's a space in the path name
Status: CLOSED INVALID
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: general (show other bugs)
Version: 1.0
Hardware: Sun Solaris
: P3 normal
Target Milestone: ---
Assignee: fop-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-11 09:54 UTC by mzumsteg
Modified: 2012-04-30 00:11 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mzumsteg 2010-08-11 09:54:06 UTC
Hi,

we've got a problem because one of our version was deployed with an ear-name with spaces in it, therefore we've got the following error message, when setting the baseURL:

ERROR VelFopProcessor:154 - IOException
java.net.MalformedURLException: Illegal character in opaque part at
index 85: wsjar:file:/opt/***/Application XYZ Archive.ear/***/WEB-INF/lib/fop/
  at org.apache.fop.apps.FOURIResolver.checkBaseURL(FOURIResolver.java:105)
  at org.apache.fop.apps.FopFactory.setBaseURL(FopFactory.java:358

So, the setBaseURL isn't working if there is a space in the path name.

NOK:
/***/Application XYZ Archive.ear/***

OK:
/***/Application_XYZ_Archive.ear/***

After chaning the ear (path name), it was working...
Comment 1 Glenn Adams 2012-04-07 01:41:22 UTC
resetting P2 open bugs to P3 pending further review
Comment 2 Glenn Adams 2012-04-07 19:24:39 UTC
white space is not permitted in URL path; you must escape by specifying %20 for SPACE
Comment 3 Glenn Adams 2012-04-30 00:11:12 UTC
batch transition resolved+invalid to closed+invalid