1. Does FOP signal any errors related to the external graphic?
[2003-07-31 09:53:18,562 INFO,STDOUT] [ERROR]: Error in XObject : Error
while loading image
http://127.0.0.1:8083/must_unfortunately_not_be_made_public.gif : class
java.lang.ClassCastException -
The URL is correct, a browser displays the .gif image.
Well, it work with BMP images (however color images appear b/w) so it
is probably a
problem with FOP's GIF decoder (?).
However FOP just can decode the GIF if I don't pass an URL but an file
system path...weird.
The URL is correct, a browser displays the .gif image.
Well, it work with BMP images (however color images appear b/w) so it
is probably a problem with FOP's GIF decoder (?).
However FOP just can decode the GIF if I don't pass an URL but an file
system path...weird.
...and jpeg works just
Weird, at this point FOP should already have successfully accessed the
content. Are you sure the server doesn't send a redirect or requires
authentication for the URL? Look into the server logs for suspicious
Yes, I am sure :-) It's the simplest HTTP GET you can imagine :)
Bug?
You are right, wget reveals text/html.
web.xml:
mime-mapping
extensiongif/extension
mime-typeimage/gif/mime-type
/mime-mapping
?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
You are right, wget reveals text/html.
-Ursprüngliche Nachricht-
Von: J.Pietschmann [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 15. August 2003 19:14
An: [EMAIL PROTECTED]
Betreff: Re: URLs in external-graphics - corrupt PDF
Psi Aushilfe3 wrote:
Yes, I am sure :-) It's the simplest
Title: Bug: number-columns-spanned ignored
Hi!
fo:tabel-cell number-columns-spanned=2 /
The span attribute is just ignored.
It might help to know the version, platform, etc. but I'm guessing
there
0.20.4, Java 1.4.2, XP.
is something wrong with your XSL-FO somewhere else (perhaps you do not
have consistent table-cell counts for the table or something?).
Hmm, no I think everything's correct. But it might be the
This gets off topic for this list by some comfortable
margin now.
I agree, however it might be interesting for people to know that the
problem is actually Jboss 2.4's WebService MBean (not tomcat) which does
read mime type from a fixed file within the dist jboss.jar
(org/jboss/web/mime.types)
