Re: [xerces2] info about some packaging changes

[Shane Curcuru <sh...@yahoo.com>]

---- you Edwin Goei <ed...@sun.com> wrote ----
> I think there are some more involved issue here.  JAXP APIs involve
both
> a parser and XSLT processor so there needs to be some coordination
> between projects which may be difficult to achieve so that a single
> xml-apis.jar file from xml-commons can be produced.  As it is now, it
> looks like Xalan has an xml-apis.jar file but it only contains the
> javax.xml.transform classes.

Actually, the current Xalan build in CVS (and I think in D13) should
have the full JAXP interfaces, including parsers, in xml-apis.jar.  It
should really be an equivalent xml-apis.jar that the
xml-commons/java/external project would produce.  Actually I just
updated the manifests for xalan.jar, xsltc.jar, and xml-apis.jar, -
hope I got them right!

> Also, there are issues w/ which version of the standard to include in
> xml-apis.jar.  I posted some emails on this on xerces-j-dev recently
and
> about whether to support the latest versions of standards or some
people
> want ones that are J2EE 1.3 compatible, for example.

Yes, coordination is going to be an issue, especially with the
effective external and very stringent J2EE requirements that some
people may want to meet.

> I don't have any answers, though.

Well, if you did, then it wouldn't be very exciting then, would it? 
8-)  (I can't believe I just typed that!)  Yes, this is a new set of
work - coordinating multiple open source projects in such a detailed
and far-reaching way.  We'll see what happens!

- Shane

=====
<eof aka="mailto:shane_curcuru@lotus.com"
 BartSays="Nobody reads these anymore."/>

__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1