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 29336 invoked from network); 30 Nov 2000 14:36:02 -0000 Received: from fw.infoplanning.net (HELO infoplanning.com) (@209.8.58.131) by locus.apache.org with SMTP; 30 Nov 2000 14:36:02 -0000 Received: (qmail 5849 invoked from network); 30 Nov 2000 14:40:12 -0000 Received: from unknown (HELO johnnybravo) (192.168.0.189) by inet with SMTP; 30 Nov 2000 14:40:12 -0000 Message-ID: <00d301c05ada$9b2afcf0$bd00a8c0@infoplanning.com> From: "Berin Loritsch" To: References: <00a601c05981$9b93c5a0$bd00a8c0@infoplanning.com> <3A263095.CD4C505C@mail.com> <00ba01c05ad3$ae5e0350$bd00a8c0@infoplanning.com> <20001130141135.J515@hydrogen.internal.luminas.co.uk> Subject: Re: SVG/PNG does not serialize Date: Thu, 30 Nov 2000 09:34:11 -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 ----- Original Message ----- From: "Paul Russell" To: Sent: Thursday, November 30, 2000 9:11 AM Subject: Re: SVG/PNG does not serialize > On Thu, Nov 30, 2000 at 08:44:37AM -0500, Berin Loritsch wrote: > > I am running Cocoon 2.0a3 current CVS on > > Windows NT 4.0 SP 5 > > IBM WebSphere 3.5 Advanced Edition SP 2 (Servlet 2.2 compliance) > > IBM HTTP Server 1.3.12 > > > > It was working in that configuration, then it stopped. > > Any useful stack traces? As I say, it's working fine here (or > at least JPEG is, and you're saying that has the same problem, > right?) That's what I'm saying. Unfortunately I am not getting _*ANY*_ stack traces. I am currently making changes to update to the newest avalonapi so that I can have hierarchical logging. I've noticed a few places where exceptions are caught and then e.printStackTrace() is called. I can't see the output of any of that when running through WebSphere. As a result, I am changing them to log.error("Class.Method", e) so I can get the stack trace through the log system.