Problems using 2.2.D14

Hi, Recently a coworker of mine tried sending the below email and I think it bounced. I'm curious if this is a known problem and/or if there's a workaround. thanks, Cliff DraperSun Microsystems, Forte Tools My opinions may or may not reflect those of my employer. ---

Re: Quick Poll: When to switch to Xerces-J 2.x?

To be clear, option B includes compatibility with Xerces 1.x. I vote +1 for B. Here are my reasons: 1) Joe and I are working on what should be some significant optimizations that I think should be in the released product: a) Reduction and reuse of RTFs. In the current base, a new D

DO NOT REPLY [Bug 5816] New: - SecurityExceptions not reported/ newTransformer newTemplates dont return

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: xml-xalan/java build.xml

curcuru 02/01/11 11:31:38 Modified:java build.xml Log: Reference new bin/xml-apis.jar file; skip compiling the xml-apis code; added skipcompat flag to ignore building 1.x compatibility-related items; bumped version number to 2.2.0 for possible release next week Revision

Re: Help please: Key() and Generated NodeSets

Rob Stanley writes: >Can any guru-types out there tell me if it is possible to use the key >function against nodes in a NodeSet generated by an extension function? The trick is the relationship between the "match" node and the "use" node. Since a NodeSet is just a collection of nodes with no str

cvs commit: xml-xalan/java build.sh build.bat

curcuru 02/01/11 11:19:34 Modified:java build.sh build.bat Log: Add new xml-apis.jar to classpath so Ant can still find JAXP classes after we update to Xerces 2.x impl jar Revision ChangesPath 1.6 +5 -1 xml-xalan/java/build.sh Index: build.sh

cvs commit: xml-xalan/java/bin xml-apis.jar

curcuru 02/01/11 11:15:55 Added: java/bin xml-apis.jar Log: DOM, SAX, JAXP interfaces from xml-commons-1.0.b1 release Revision ChangesPath 1.1 xml-xalan/java/bin/xml-apis.jar <>

cvs commit: xml-xalan/c/src Makefile.in

dbertoni02/01/11 10:44:07 Modified:c/srcMakefile.in Log: Added another missing -I. Revision ChangesPath 1.79 +1 -1 xml-xalan/c/src/Makefile.in Index: Makefile.in === RCS file: /home/cv

Re: Xalan using Code Warrior

We've also got Mac builds of Xalan 1.2 compiling under CodeWarrior. The main problem I ran into was the one mentioned at: http://marc.theaimsgroup.com/?l=xalan-dev&m=99911132205441&w=2 I've reported this to MetroWerks. Working around this required about 125 patches to the code to use the g

cvs commit: xml-xalan/java/src/org/apache/xalan/processor XSLProcessorVersion.java

dleslie 02/01/11 08:57:20 Modified:java/src/org/apache/xalan/processor XSLProcessorVersion.java Log: updated release number to 2.2. Revision ChangesPath 1.34 +1 -1 xml-xalan/java/src/org/apache/xalan/processor/XSLProcessorVersion.java Index: XSLProcessorV

cvs commit: xml-xalan/java/src/org/apache/xalan/res XSLTInfo.properties

dleslie 02/01/11 08:57:05 Modified:java/src/org/apache/xalan/res XSLTInfo.properties Log: updated release number to 2.2. Revision ChangesPath 1.27 +1 -1 xml-xalan/java/src/org/apache/xalan/res/XSLTInfo.properties Index: XSLTInfo.properties ==

cvs commit: xml-xalan/java commits.xml

dleslie 02/01/11 08:52:01 Modified:java commits.xml Log: interim update for next release Revision ChangesPath 1.35 +393 -404 xml-xalan/java/commits.xml Index: commits.xml === RCS file: /ho

RE: Quick Poll: When to switch to Xerces-J 2.x?

+1 on A ... it's been almost 8 months since the last minor release! - Gulli > -Original Message- > From: Shane Curcuru [mailto:[EMAIL PROTECTED]] > Sent: 11. januar 2002 15:05 > To: [EMAIL PROTECTED] > Subject: Quick Poll: When to switch to Xerces-J 2.x? > > > OK, here's a n

Quick Poll: When to switch to Xerces-J 2.x?

OK, here's a non-binding request for all xalanites. Please vote +1 for any *one* lettered option below, along with any comments you have; replies ASAP are better since we need to plan our builds out soon! Vote for {A | B | C}: A. Ship a final Xalan 2.2 build soon (mid-Jan) with: -- existing Xe

Help please: Key() and Generated NodeSets

Hi, Can any guru-types out there tell me if it is possible to use the key function against nodes in a NodeSet generated by an extension function? I guess some clever use of generate-id in a for-each might work? Thanks, Rob Stanley Geac Enterprise Solutions Limited