Shane wrote: > To-do's for Xalan include: updating the javax.xml.transform > code in the xml-commons tck-jaxp-1_2_0 branch with whatever > similar updates are needed; testing xml-xalan CVS with an > xml-apis.jar built from these sources; and if all's well, > asking for an xml-commons/./external release so that we can > checkin the static xml-apis.jar and related sources into > xml-xalan.
I have updated the javax.xml.transform code in the xml-commons tck-jaxp-1_2_0 branch. It now contains the same code that was in the RIVERCOURT1 branch, plus a patch to StreamSource to use the same filename to URI conversion used by the javax.xml.parser package. Smoketest of xalan passes with an xml-apis.jar built from these sources. Shane wrote: > Note the xml-commons community will need to develop a > distribution structure for an 'external' release now > that xml-commons will be (unless someone disagrees) > shipping it's components separately (external/which/resolver > for now). Ilene. ---- on [EMAIL PROTECTED] [EMAIL PROTECTED] wrote ---- > I've created a new branch (tck-jaxp-1_2_0) containing code that's > JAXP 1.2 compliant and solves a number of bugs with code from > HEAD (especially having to do with security handling and robustness > with filenames containing characters such as spaces). I also > populated HEAD with this by mistake; sorry about that. :( I think > I've successfully reverted that error, but if someone could verify > that, I'd appreciate it greatly. > Note that I haven't updated the javax.xml.transform API on the > branch, nor the branch's manifest file; I thought I'd leave that to > the experts in such things. :)
