Hi Vivek,
The most obvious way to get what you want--which I presume is just a
xercesImpl.jar--is to use our "jar" build target. Then you'll get one
jarfile which you can use in conjunction with xml-apis.jar if you like.
We're definitely aware of the fact that there's much API duplication
between ourselves and commons (DOM and SAX are also duplicated, and in the
SAX case at least the delta is significant). But there are a few
constraints we're under:
- There are people who want to use us in J2SE 1.4 implementations or in
J2EE 2.0 implementations. But to be conformant we have to support a very
precise set of features in our API's--and unfortunately the commons code
doesn't comply. (So far as I know this is only relevant to SAX, where
commons SAXException has different signatures from ours).
- We neither implement nor use the transform part of the JAXP API.
Therefore, it's not only unnecessary but positively misleading for us to
ship it. From this vantage point, xml-apis.jar looks very sensible as a
standard for XSLT engines but not for parsers...
Obviously, work needs to be done to sort this stuff out. But that's the
situation as it stands today.
Hope that helps,
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: [EMAIL PROTECTED]
Vivek Pandey
<vivek.pandey@ To: [EMAIL PROTECTED]
sun.com> cc: Vivek Pandey <[EMAIL PROTECTED]>
Subject: Building xercesImpl.jar from
xml-common
04/04/2002
07:55 PM
Please respond
to
xerces-j-dev
xerces has xml-api (javax) sources and compiles them and references them
in the build.
I am trying to compile xerces with xml-commons jars. The only way i am
able to do is by changing xml-xerces/java/build.xml (to compile only for
target 'org' excluding 'javax') file.
Below is the diff of xml-xerces/java/build.xml, introduced new target
compile.xerces, which compiles src/org. This means i can set a classpath
pointing to xml-common jars so that it resolves xmlapi related
references from it. Everything looks fine with this change.
There can be better way of doing it:
-include xml-api.jar file in xml-xerces/tools.
-Remove javax sources or do not compile them.
-add a path id or property to refer to xmlapi.jar file. This
path id can be overridden from the other build file which invokes this
build.
I think xerces/java/build.xml should be modified to take xml-api.jar
from xml-commons instead of from native source. Because xerces native
javax package can be out of sync with xml-commons javax package.
Does anyone know can help how to fix this.
thanks,
-vivek.
--------------------
Index: build.xml
===================================================================
RCS file: /home/cvspublic/xml-xerces/java/build.xml,v
retrieving revision 1.74
diff -c -w -r1.74 build.xml
*** build.xml 4 Mar 2002 12:35:42 -0000 1.74
--- build.xml 5 Apr 2002 00:04:49 -0000
***************
*** 182,187 ****
--- 182,207 ----
</target>
<!--
=================================================================== -->
+ <!-- Compile xerces source and use external
jaxp-api
-->
+ <!--
=================================================================== -->
+ <target name="compile.xerces" depends="prepare-src">
+ <copy todir="${build.dest}">
+ <fileset dir="${build.src}"
+ includes="**/*.res, **/*.properties">
+ </fileset>
+ </copy>
+
+ <javac srcdir="${build.src}/org"
+ excludes="**/RevalidatingDOMParser.java"
+ destdir="${build.dest}"
+ debug="${debug}"
+ deprecation="${deprecation}"
+ optimize="${optimize}"
+ includeAntRuntime="true"
+ includeJavaRuntime="true"/>
+ </target>
+
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
