AW: MalformedURLException when using relative paths

2008-05-22 Thread Preuss, Jacqueline - ENCOWAY
Hi, 

thanks for your replies. I tried: file:pdf_test, file://pdf_test Works both for 
me, because we have our own URI Resolver Implementation. Now, we have to check 
whether the case path starts with file:// and remove this.

Regards,
Jacqueline.

 -Ursprüngliche Nachricht-
 Von: Ted Young [mailto:[EMAIL PROTECTED]
 Gesendet: Mittwoch, 21. Mai 2008 22:41
 An: fop-users@xmlgraphics.apache.org
 Betreff: RE: MalformedURLException when using relative paths
 
 
 I know it works with FOP .94 since I am doing exactly this right now.  :-)
 
 Ted
 
 -Original Message-
 From: J.Pietschmann [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, May 21, 2008 3:11 PM
 To: fop-users@xmlgraphics.apache.org
 Subject: Re: MalformedURLException when using relative paths
 
 Ted Young wrote:
  Yes, it supports relative, but relative URLs not relative file paths.  So,
  what you want it:
  file:pdf_test
 
 Everything starting with file: (or anything else which looks like
 an URI scheme) is by specification an absolute URL. The string
 file:pdf_test is not a valid URL at all, although some libraries
 will try to interpret it the way you do. I'm not sure whether FOP
 does it, and I'm too tired to check the URI resolver class right
 now.
 
 J.Pietschmann
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



MalformedURLException when using relative paths

2008-05-21 Thread Preuss, Jacqueline - ENCOWAY
Hi!

 

We're just upgrading from fop_0.92 to fop_0.95beta. In our Fop
Configuration File we defined a base and a font-base like this:

 

base./pdf_test/base

font-base./pdf_test/pdf_fonts/font-base

 

With 0.92 everything works fine but with the newer version we get the
following exception:

 

java.net.MalformedURLException: no protocol: ./pdf_test/

at java.net.URL.init(URL.java:567)

at java.net.URL.init(URL.java:464)

at java.net.URL.init(URL.java:413)

at
org.apache.fop.apps.FopFactory.checkBaseURL(FopFactory.java:339)

at
org.apache.fop.apps.FopFactory.setBaseURL(FopFactory.java:355)

at
org.apache.fop.apps.FopFactoryConfigurator.configure(FopFactoryConfigura
tor.java:116)

at
org.apache.fop.apps.FopFactoryConfigurator.setUserConfig(FopFactoryConfi
gurator.java:231)

at
org.apache.fop.apps.FopFactoryConfigurator.setUserConfig(FopFactoryConfi
gurator.java:203)

at
org.apache.fop.apps.FopFactory.setUserConfig(FopFactory.java:637)

 

Are relative paths not allowed anymore? What can we do to solve this?
Are there any suggestions available?

 

Regards,

Jacqueline.



Re: MalformedURLException when using relative paths

2008-05-21 Thread J.Pietschmann

Ted Young wrote:

Yes, it supports relative, but relative URLs not relative file paths.  So,
what you want it:
file:pdf_test


Everything starting with file: (or anything else which looks like
an URI scheme) is by specification an absolute URL. The string
file:pdf_test is not a valid URL at all, although some libraries
will try to interpret it the way you do. I'm not sure whether FOP
does it, and I'm too tired to check the URI resolver class right
now.

J.Pietschmann


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: MalformedURLException when using relative paths

2008-05-21 Thread Ted Young
I know it works with FOP .94 since I am doing exactly this right now.  :-)

Ted

-Original Message-
From: J.Pietschmann [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 21, 2008 3:11 PM
To: fop-users@xmlgraphics.apache.org
Subject: Re: MalformedURLException when using relative paths

Ted Young wrote:
 Yes, it supports relative, but relative URLs not relative file paths.  So,
 what you want it:
 file:pdf_test

Everything starting with file: (or anything else which looks like
an URI scheme) is by specification an absolute URL. The string
file:pdf_test is not a valid URL at all, although some libraries
will try to interpret it the way you do. I'm not sure whether FOP
does it, and I'm too tired to check the URI resolver class right
now.

J.Pietschmann


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]