Hi Dims, Just to make sure there's no possibility of confusion: No version of Xerces builds xml-apis.jar. Xerces2 builds an API jar file that contains a subset of the APIs represented in xml-apis.jar, and it gives that jar a different name (xmlParserAPIs.jar for now) to make absolutely sure users know what it's for.
As to what's stored in xml-commons: my preference would be for us to wait until DOM level 3 reaches a more stable level and SAX 2.0 finally reaches r2 before deciding what to do. I suspect it probably will make sense to upgrade the API's in xml-commons at that point, but once we get there we'll have a better view of the lay of the land; no sense in deciding that while these API's are still in beta or working draft. Cheers, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 905-413-3519, T/L 969-3519 E-mail: [EMAIL PROTECTED] Davanum Srinivas <[EMAIL PROTECTED]> on 11/30/2001 07:53:16 AM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: [xerces2] info about some packaging changes Shane, Edwin, #1: I think xml-apis.jar should contain the same thing whether it is built by Xalan project or Xerces Project. #2: My vote is to include latest DOM and SAX Standards (Not necessarily J2EE-1.3 compatible). We cannot and should not stop moving forward just because SUN picked up a snapshot to bundle with J2EE. Thanks, dims --- Edwin Goei <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > > > [snip] > > I.e. to me the point is that we're agreeing to ship *stable* > > externally-defined standards-based files in a jar named xml-apis.jar. Any > > other files a project wants to use should go in their implementation jar, > > or somewhere else; and the xml-apis.jar should always include it's full > > contents, and should match very closely (except for last-minute bugfixes) > > the same code as in xml-commons. > > > > Am I making any sense? Does anyone else agree with me? (Note, they're > > separate questions!) One other important issue is we should have some > > manifest packaging expert help us all implement some better documented and > > finely-grained versioning info in our manifests; I've started in > > xml-xalan/java/src/MANIFEST.MF but it needs updating and I'm not sure I've > > gotten it quite right yet. > > 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. > > 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. > > I don't have any answers, though. > > -Edwin > > --------------------------------------------------------------------- > In case of troubles, e-mail: [EMAIL PROTECTED] > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > ===== Davanum Srinivas - http://jguru.com/dims/ __________________________________________________ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1 --------------------------------------------------------------------- In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
