James Duncan Davidson wrote:
>
> > What I would suggest is that we replace xml.jar with one based on a
> > suitable subset of xerces.jar. At the same time we replace the logic in
> > org.apache.tools.ant.Parser which currently looks for a properties file to
> > attempt to dynamically load JAXP. If that is not found, we default to
> > xerces.
>
> The defaulting out to Xerces isn't really necessary now that we have JAXP
> support in Xerces. Just use the JAXP libraries and all it requires is that a
> JAXP enabled browser (which Xerces is) be in your classpath. The logic
> should catch a ClassNotFoundException on the initial call to create a
> SAXParserFactory so that a reasonable error message saying "Put a JAXP
> enabled browser such as Xerces or Project X into your classpath!" can be
> output.
+1 to this!!!! Let's enforce JAXP a little.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<stefano@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
Come to the first official Apache Software Foundation Conference!
------------------------- http://ApacheCon.Com ---------------------
|