cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Berin Loritsch" <blorit...@infoplanning.com>
Subject Re: ImageEncoder and FOPSerializer
Date Mon, 18 Dec 2000 18:29:49 GMT
All of the sudden it is working again!  I wonder if it had to do
with the update to Xalan?  It also could have been a classpath issue.
Sigh.

We need better detection of runtime errors.

----- Original Message ----- 
From: "Berin Loritsch" <bloritsch@infoplanning.com>
To: <cocoon-dev@xml.apache.org>
Sent: Monday, December 18, 2000 11:55 AM
Subject: ImageEncoder and FOPSerializer


> There is still an uncaught runtime exception with the ImageSerializers
> and FOPSerializers that only manifests with WebSphere.  What Kind
> of RunTime exceptions would be caught there?  This is with Cocoon 2.
> 
> org.apache.cocoon.generation.FileGenerator (org.apache.cocoon.generation.FileGenerator@bd16a514)
> DEBUG   11542   [cocoon  ] (Worker#12): ComponentPool retrieved org.apache.cocoon.serialization.FOPSerializer
> (org.apache.cocoon.serialization.FOPSerializer@9e712515)
> DEBUG   11547   [cocoon  ] (Worker#12): ComponentPool returned org.apache.cocoon.serialization.FOPSerializer
> (org.apache.cocoon.serialization.FOPSerializer@9e712515)
> DEBUG   11547   [cocoon  ] (Worker#12): ComponentPool returned org.apache.cocoon.generation.FileGenerator
> (org.apache.cocoon.generation.FileGenerator@bd16a514)
> 
> ---------------------------------------
> If you lust for Ham and Eggs, you have
> committed breakfast in your heart
> already.   -- C. S. Lewis


Mime
View raw message