You are viewing a plain text version of this content. The canonical link for it is here.
Posted to batik-dev@xmlgraphics.apache.org by Cameron McCormack <ca...@mcc.id.au> on 2006/09/05 03:25:54 UTC
Bundled Xerces (was Re: DO NOT REPLY [Bug 40393] - Too many JSVGComponent on a single page cause OutOfMemory exception)
(Switching to batik-dev…)
Thomas DeWeese:
> The only one above that is a hard dependency is xml-apis
> which is kind of required for an XML implementation.
> js.jar & pdf-transcoder.jar are only required if you are
> using their functionality. The Xerces dependency is
> configurable (simply requires a SAX 2 interface,
> and has recently moved to JAXP).
I forget: what is Xerces needed for? Is it just the SAX parser, because
Java 1.3 didn’t come with one?
I wonder if we shouldn’t provide two distributions, one which includes
Xerces (and Xalan, for XPath) to work on Java 1.3, and another that
doesn’t, since Java 1.4 already has them.
--
Cameron McCormack, http://mcc.id.au/
xmpp:heycam@jabber.org ▪ ICQ 26955922 ▪ MSN cam@mcc.id.au
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org
Re: Bundled Xerces
Posted by Cameron McCormack <ca...@mcc.id.au>.
Thomas DeWeese:
> Well, so this raises an interesting question. Right now our
> code base will compile with either JDK 1.4 or 1.3 but you don't
> get the same thing when you do this. Will a JDK 1.4 build run
> cleanly on JDK 1.3? I would suspect not since the JGVTComponent
> will try and register a scroll wheel event handler which doesn't
> exist in JDK 1.3.
You are right, it doesn’t. I wonder how many users of Batik actually
need 1.3 support—it must be declining.
> This is fine for development/source dist since the build
> tools figure this all out for us, but what about when we go
> to make a binary distribution? I think it would be fairly ugly to
> have two binary distributions (one for JDK 1.3, and one for
> JDK 1.4+). Is that commonly done?
That’s a good point. We haven’t had a release since that mouse wheel
stuff went in there, have we? It seems that FOP have 1.3 and 1.4
versions of their release:
http://apache.planetmirror.com/dist/xmlgraphics/fop/
--
Cameron McCormack, http://mcc.id.au/
xmpp:heycam@jabber.org ▪ ICQ 26955922 ▪ MSN cam@mcc.id.au
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org
Re: Bundled Xerces
Posted by th...@kodak.com.
Hi Cameron,
Cameron McCormack <ca...@mcc.id.au> wrote on 09/04/2006 09:25:54 PM:
> Thomas DeWeese:
> > The Xerces dependency is configurable (simply requires a SAX 2
> > interface, and has recently moved to JAXP).
>
> I forget: what is Xerces needed for? Is it just the SAX parser, because
> Java 1.3 didn?t come with one?
Yes, this is all that it is needed for.
> I wonder if we shouldn?t provide two distributions, one which includes
> Xerces (and Xalan, for XPath) to work on Java 1.3, and another that
> doesn?t, since Java 1.4 already has them.
Well, so this raises an interesting question. Right now our
code base will compile with either JDK 1.4 or 1.3 but you don't
get the same thing when you do this. Will a JDK 1.4 build run
cleanly on JDK 1.3? I would suspect not since the JGVTComponent
will try and register a scroll wheel event handler which doesn't
exist in JDK 1.3.
This is fine for development/source dist since the build
tools figure this all out for us, but what about when we go
to make a binary distribution? I think it would be fairly ugly to
have two binary distributions (one for JDK 1.3, and one for
JDK 1.4+). Is that commonly done?
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org