From bloritsch@infoplanning.com Mon Dec 18 16:57:49 2000 Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 32249 invoked from network); 18 Dec 2000 16:57:49 -0000 Received: from fw.infoplanning.net (HELO infoplanning.com) (@209.8.58.131) by locus.apache.org with SMTP; 18 Dec 2000 16:57:49 -0000 Received: (qmail 26792 invoked from network); 18 Dec 2000 16:59:59 -0000 Received: from unknown (HELO johnnybravo) (192.168.0.189) by inet with SMTP; 18 Dec 2000 16:59:59 -0000 Message-ID: <01e901c06913$6596ca50$bd00a8c0@infoplanning.com> From: "Berin Loritsch" To: Subject: ImageEncoder and FOPSerializer Date: Mon, 18 Dec 2000 11:55:59 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N 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