cvs commit: xml-xalan/c/src/XalanExe XalanExe.cpp

dbertoni2002/08/13 22:12:36 Modified:c/src/XalanExe XalanExe.cpp Log: Implemented new command line options. Revision ChangesPath 1.11 +55 -0 xml-xalan/c/src/XalanExe/XalanExe.cpp Index: XalanExe.cpp

cvs commit: xml-xalan/c/src/XalanSourceTree XalanSourceTreeContentHandler.cpp

dbertoni2002/08/13 19:53:58 Modified:c/src/XalanSourceTree XalanSourceTreeContentHandler.cpp Log: Work-around for Xerces bug 3111. Revision ChangesPath 1.13 +7 -0 xml-xalan/c/src/XalanSourceTree/XalanSourceTreeContentHandler.cpp Index: XalanSourceTreeCont

Re: Xalan Extension Integration with XSLTC

> 8. evaluate extension > After investigation, I think it is NOT possible to implement the evaluate > extension in XSLTC, given the design constraints of XSLTC. XSLTC parses an > XPATH expression into DOM iterator calls at compile time. However, the > expression string passed to the evaluate e

cvs commit: xml-xalan/java/src/org/apache/xalan/xsltc/trax DOM2SAX.java TemplatesHandlerImpl.java TemplatesImpl.java TransformerFactoryImpl.java TransformerHandlerImpl.java

zongaro 2002/08/13 14:21:14 Modified:java/src/org/apache/xalan/templates Tag: XSLTC_DTM ElemValueOf.java java/src/org/apache/xalan/xsltc Tag: XSLTC_DTM TransletOutputHandler.java java/src/org/apache/xalan/xslt

cvs commit: xml-xalan/java/src/org/apache/xalan/xsltc/dom XSLTCDTMManager.java

zongaro 2002/08/13 14:20:24 Modified:java/src/org/apache/xalan/xsltc/dom Tag: XSLTC_DTM XSLTCDTMManager.java Log: Some minor code clean-up. Revision ChangesPath No revision No revision 1.1.2.2

cvs commit: xml-xalan/java/src/org/apache/xalan/xsltc/trax TransformerImpl.java

zongaro 2002/08/13 14:19:08 Modified:java/src/org/apache/xalan/xsltc/trax Tag: XSLTC_DTM TransformerImpl.java Log: Picked up latest changes from MAIN branch, as well as a fix for id/key from revision 1.42 that I merged incorrectly. Also, in getDOM method,

DO NOT REPLY [Bug 11221] - Variable node-sets in x-path predicates work incorrectly in XLTC

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_b

Re: Bug found in 2.4.1D relating to the key() fn

Hi Nancy, I was able to reproduce the problem you're seeing, and I am looking at it. In the meantime, could you please open a bug report in bugzilla and include your attachment. Thanks! Ilene Seelemann. -- XSLT Development, IBM Toronto Lab

cvs commit: xml-xalan/java/src/org/apache/xalan/xsltc/compiler ParameterRef.java Expression.java VariableRef.java

tmiller 2002/08/13 12:12:33 Modified:java/src/org/apache/xalan/xsltc/compiler ParameterRef.java Expression.java VariableRef.java Log: bug fix for bugzilla 11221, MK053 Revision ChangesPath 1.11 +7 -5 xml-xalan/java/src/org/apache/xalan/

Xalan Extension Integration with XSLTC

Hi, I will be working on improving the extension support in Xalan. One of the working items is the XSLTC integration. The ultimate goal is to have consistent syntax for extensions, so that the transformation is transparent and the user can use the same stylesheet, without considering which transf

DO NOT REPLY [Bug 11661] - xsl:key very very slow!

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_b

Bug found in 2.4.1D relating to the key() fn

Xalan Developers: I found the following bug in xalan 2.4.1D The key() function throws an exception when called in the context of a local variable. Here is an extremely small transform that can be used to reproduce the problem. I have verified that this transform works fine in 2.3.1 but does n

DO NOT REPLY [Bug 11661] - xsl:key very very slow!

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_b

DO NOT REPLY [Bug 11661] - xsl:key very very slow!

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_b

DO NOT REPLY [Bug 11661] - xsl:key very very slow!

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_b

DO NOT REPLY [Bug 11661] - xsl:key very very slow!

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_b

DO NOT REPLY [Bug 11661] - xsl:key very very slow!

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_b

DO NOT REPLY [Bug 11661] New: - xsl:key very very slow!

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_b

DO NOT REPLY [Bug 11648] New: - document() doesn't work from a Templates

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_b