Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 2980 invoked by uid 500); 28 May 2001 11:06:23 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Delivered-To: moderator for cocoon-dev@xml.apache.org Received: (qmail 94691 invoked from network); 28 May 2001 10:47:14 -0000 Message-ID: <029801c0e763$79979650$1001000a@centervilletech.com> From: "Colin Britton" To: References: <991034224.3b11fb706d587@mail.otego.com> Subject: Re: [C2]: Final list for beta Date: Mon, 28 May 2001 06:21:52 -0400 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-OriginalArrivalTime: 28 May 2001 10:46:39.0413 (UTC) FILETIME=[79979650:01C0E763] X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N The list we need is provided in the manifest of the rasterizer jar. It is extensive IIRC only one or two of the jars are not needed, for me when I was working with this it was easier to roll up all of them than save the 100k of the missing couple. rgds CB ----- Original Message ----- From: "Giacomo Pati" To: Sent: Monday, May 28, 2001 3:17 AM Subject: Re: [C2]: Final list for beta > BTW: Do we need the huge batik-all.jar at all? I've seen Batik splits up into > several jars which leads me to think we only need a few of them. > > Giacomo > > Quoting giacomo : > > > On Sun, 27 May 2001, Ross Burton wrote: > > > > Hi Ross :) > > > > > Colin Britton wrote: > > > > > > > > > > > > > > - can we make Batik act nicer? It's throwing alot of Exceptions > > which > > > > > might be because it was not designed to run in a server/servlet > > > > > environment or we use it the wrong way? Is anyone on the batik > > list > > > > > or more familiar with it? Batik starts with a > > TranscoderException > > > > > encloseing a null Exception and one that states "Connection > > reset > > > > > by peer". Any suggestions? > > > > > > > > Our SVGSerializer works by building a DOM document object and > > passing this > > > > to Batik. This was because when the first Batik Transcoder was made > > > > available that was the only way you could do it. Since that first > > release > > > > that the SVGSerializer was based on was produced the transcoder > > interface > > > > was rewritten. In that new interface came support for a > > > > org.xml.sax.XMLReader and I believe full SAX2 support. It would > > probably a > > > > good idea to change to this interface rather than the current > > > > implementation. > > > > > > The SAX interfaces are there because I bugged them enough. :-) When > > > they first appeared they just backed straight onto a DOM builder - but > > > that was quite a while ago. Tomorrow I'll try and get the SVG stuff > > up > > > to date with the Batik 1.0 release. > > > > That's cool, thanks. > > > > Giacomo > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > > For additional commands, email: cocoon-dev-help@xml.apache.org > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org