Jeff Turner wrote:
I'd be interested to know if any other users experience this problem, and
also why Cocoon needs a recompiled FOP jar in the first place.
Me too, as I'm experiencing the exact same problem as you described,
with jimi.jar on the classpath. Even worse, there isn't a supported
On Wed, Sep 10, 2003 at 12:59:07PM +0200, Steven Noels wrote:
Jeff Turner wrote:
I'd be interested to know if any other users experience this problem, and
also why Cocoon needs a recompiled FOP jar in the first place.
Me too, as I'm experiencing the exact same problem as you described,
The exception below was the reason for building our own FOP and not taking
the released fop.jar. Immediately before releasing Cocoon 2.1 somebody told
us that Cocoon's FOP and Batik are incompatible, but a rebuild of FOP using
Cocoon's Batik helped, so I did it too and committed the fop.jar.
I
Joerg Heinicke wrote:
I know FOP should be built with JAI and JIMI and I thought I have done
it. Sorry for any inconvenience.
No problem - it brings a sense of reality about our user base and their
upgrade frequency, when we discover these things ourselves only after a
few weeks or so. ;-)
Following up on this, I am unable to replicate within Cocoon's webapp.
The minimal.fo.xml page renders fine with an embedded image. So I won't
tinker with src/blocks/fop/lib/*.
However Forrest continues to break when using Cocoon's version of FOP, so
I'll switch Forrest's jar to that from the
On Tue, Sep 02, 2003 at 11:27:30PM +0200, Christian Geisert wrote:
[EMAIL PROTECTED] schrieb:
jefft 2003/08/31 02:41:53
Modified:etc/cocoon_upgrade upgrade_cocoon_jars.sh
Log:
Don't upgrade FOP, as 0.20.5 seems to have a JAI dependency hardcoded
Huh?
FOP 0.20.5 is build
