The best way I know of to support this on a headless server is using a
virtual frame buffer (Xvfb) which comes with XFree. I think Sun is planning
to have it fixed in JDK 1.4. See
http://developer.java.sun.com/developer/bugParade/bugs/4281163.html for more
info.
-Kelly
> -Original Message---
Peter,
Another reason is for the auto-generation of the property handling classes.
Also, I beleive one of the very early versions of Ant which was used
required the source files and destination to be the same, and just to make
cleanup easier the build file was written to copy them to the build
di
You need FOP 0.18 or later to use the java -jar command line style.
-Kelly
On Thu, Jun 07, 2001 at 02:30:12PM +0100, Kin-Yip Tsang wrote:
> Hello,
>
> i've downloaded fop-bin-0_17_0.jar and tried to transform a fo file to
> pdf but failed. i saved the fo.jar (i've renamed it) to the classpath
> -Original Message-
> From: Alex McLintock [mailto:[EMAIL PROTECTED]]
>
> I'm not going to argue whether or not a rewrite is a good
> idea but it is
> pointless to expect business to pay for the rewrite. Business
> is all about
> immediate results and immediate profit. Just about eve
I seem to remember fixing some of the possible problems in a more recent
release. And I know Keiron or Arved also fixed a problem with a static page
numbering variable that would cause problems like that.
Try 0.18.1 and see if it works better for your application.
One approach for tracking down
I added this to CVS.
-Kelly
> -Original Message-
> From: Chris Burkey [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 18, 2001 9:32 AM
> To: [EMAIL PROTECTED]
> Subject: small code fix
>
>
> Hello,
>
> Here is one line of code added to latest CVS, as shown:
>
> org.apache.fop.f
Scott,
Is it possible you have an older version of FOP checked out and didn't do a
"build clean"? That's about the only thing I can think of that might be
causing that ambiguous class error. I will try a clean build using Xalan2
from CVS and see what happens.
-Kelly
> -Original Message
ending on if I write a message out before or
after this template does its work. I don't have time to dig into this any
more today however. Hopefully someone on the Xalan team will be able to look
into this.
-Kelly
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTE
Hi Andre,
XSL:FO doesn't specify any form widgets such as you want. This is something
which currently is only implemented in HTML browsers. There is a working
draft spec for XForms which provides form widgets in the context of XHTML,
but I think it would allow for mixing form widgets into a XSLFO
I am wondering if anyone objects to an update of our bundled dependencies:
Xerces 1.2.3 -> 1.4.0
Xalan 2.0.0 -> 2.1.1-dev (neccessary to fix the Gump build issues Scott
and I have been discussing), should be upgraded to a final released version
of xalan-2.1.1 or 2.2.0 (whatever they decide to c
It sounds like you just need to run a transform using Xalan on the xml to
get the FO tree, and pass that FO tree to FOP using Driver.setInputSource().
See the Xalan web page for examples of doing the tranform programatically.
-Kelly
> -Original Message-
> From: sravan kumar [mailto:[EMAI
+1 for committing it. I've always thought there was something a little off
in our line spacing, I just couldn't put my finger on it.
Just because we have a test suite, doesn't mean we should let them hold us
up from fixing problems :-) I've encountered this before on other projects
that test by c
Scott,
I'm not seeing any problems due to this redirect change with the FOP build
currently. What was the problem you were seeing?
-Kelly
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 19, 2001 3:14 PM
> To: [EMAIL PROTECTED]
> Cc: Fop-De
As a workaround, you can probably fork out a new 1.2 JVM from 1.1 in order
to run stuff like FOP+Batik that requires the 1.2 API. Integration that way
isn't exactly clean, but it is a valid workaround that's been used many
times elsewhere :-)
Upgrading from 1.1 to 1.2 is probably a much much bigg
I don't know if anyone has done any extensive testing of concurrency with
FOP, so please let us know what problems you run into (the IndexOutOfBounds
for example), either via this list, or better yet, via Bugzilla so we can
track and fix the issues. I've fixed a few places where I found concurrenc
This issue seems familiar. I seem to remember working around something
similar with redirects when we went from Xalan1 to Xalan2 in the FOP build.
Make Xalan2 do "the right thing", and we'll fix our build if there's an
issue because it was relying on a bug in something else we import.
I'm glad G
JDK 1.3.1 on Linux is very finicky about what versions of libraries it works
with. I've seen all kinds of problems with Redhat 7.0, 7.1, and Debian
latest. Redhat 6.2 is the only version I've found to be fully stable for all
JDK's I've ever tested.
-Kelly
> -Original Message-
> From: Pet
17 matches
Mail list logo
