Re: FWD: XSLTC and iterator problems

John, Your analysis is very good. Some cloned iterators cannot be reset, and causes a problem when they are passed by referenced (ie. cloned). Making all clones deep, and thereby allowing the clone to be reset, should make this problem go away. But I don't like the idea of removing setStartNode(

FWD: XSLTC and iterator problems

John Howard wrote: > > Morten, > > I think I have a nice tight answer to your question about the different > behaviours when the iterator is wrapped in a reference. I can do this by > refering to the enclosed Param_Forward.java file which is the decompiled > translet from bug#3238 (it won't comp

XNodeSet.getStringFromNode()

Is there a particular reason that the XNodeSet.getStringFromNode() -- as well as getNumberFromNode() are now package-private rather than public? I have several apps that are using the XNodeSet code assuming that that code would continue to be available and updated as required by changes in stan

DO NOT REPLY [Bug 3296] - a Segmentation fault when runing samples of xalan-j_2_2_D9

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

Re: Result Tree Fragments and Nodesets

Thanks for the suggestion. That works and seems to be the best solution so far. But I still don't like RTFs... :-) Chris Rick Bullotta wrote: >One Xalan-specific approach would be to use xalan:evaluate() in the select >expression of the variable. You could build the XPath expression in a >v

RE: No getOwnerElement() in DTMNodeProxy?

> I can understand why many of the methods throw exceptions (because the > DTM is read-only), but why is this getOwnerElement() unimplemented? Or, more to the point, what would be wrong with: public final Element getOwnerElement() { if (dtm.getNodeType(node) == DTM.ATTRIBUTE_NODE) {

No getOwnerElement() in DTMNodeProxy?

I can understand why many of the methods throw exceptions (because the DTM is read-only), but why is this getOwnerElement() unimplemented? For that matter, getOwnerDocument() seems innocuous enough, too... Paul Brown FiveSight Technologies, Inc.

DO NOT REPLY [Bug 3731] New: - position() returns incorrect value--returns position()*2 for child nodes

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/c/src/XSLT ElemAttribute.cpp ElemChoose.cpp ElemComment.cpp ElemCopy.cpp ElemElement.cpp ElemFallback.cpp ElemForEach.cpp ElemIf.cpp ElemLiteralResult.cpp ElemMessage.cpp ElemOtherwise.cpp ElemPI.cpp ElemTemplate.cpp ElemTemplateElement.cpp ElemTemplateElement.hpp ElemValueOf.cpp ElemVariable.cpp ElemWhen.cpp

dbertoni01/09/19 14:20:47 Modified:c/src/XSLT ElemAttribute.cpp ElemChoose.cpp ElemComment.cpp ElemCopy.cpp ElemElement.cpp ElemFallback.cpp ElemForEach.cpp ElemIf.cpp ElemLiteralResult.cpp ElemMessage.cpp ElemOther

RE: Result Tree Fragments and Nodesets

Hi Chris, I'm lost here because I'm not sure what you want: 1. You can make variable with and access first data with xpath expression: or and access first data with xpath expression: It will select only one and existing group 2. You can specify as complicated x-path as you need. There're

RE: Result Tree Fragments and Nodesets

One Xalan-specific approach would be to use xalan:evaluate() in the select expression of the variable. You could build the XPath expression in a variable, and use it as the parameter to the xalan:evaluate() function. Pseudocode would look like: /doc/group1 /doc/group2

Re: Result Tree Fragments and Nodesets

But the problem comes in when I can't do a simple select. I don't want to select both subtrees - I want to pick one or the other. This is a really ugly part of XSLT that I hope will have some resolution at some point. There seems to be no way to get the equivalent (functional and performance

DO NOT REPLY [Bug 1031] - Recursive XPath iteration is 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_bu

RE: Result Tree Fragments and Nodesets

Hi Chris, Probably in your case you can just create node-set variable, like or any other node-set expression you need. You can put this code on the top-level (right inside xsl:stylesheet element) and then reference it as node-set, for instance: or Thanks, Dmitry -Original Messa

DO NOT REPLY [Bug 2802] - Unimplemented interface method: tFactory.newTransformer(xslSource)

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

DO NOT REPLY [Bug 2945] - Problem of getting of set of nodes: select="ancestor::myNode[@id='main']|ancestor::myNode[@id='aux']

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

Re: Result Tree Fragments and Nodesets

Does copy-of really make a copy? I really don't want that extra overhead of copying the entire subtree just so I can reference it. Is there a better way to accomplish this? (setting a variable to a subtree so that it can be easily reference later). Thanks, Chris Voytenko, Dimitry wrote:

cvs commit: xml-xalan/java/src/org/apache/xalan/xsltc/compiler RelationalExpr.java

tmiller 01/09/19 12:25:29 Modified:java/src/org/apache/xalan/xsltc/compiler RelationalExpr.java Log: bug fix 2838, (namedtemplate test) Revision ChangesPath 1.8 +8 -2 xml-xalan/java/src/org/apache/xalan/xsltc/compiler/RelationalExpr.java Index: Relationa

DO NOT REPLY [Bug 3296] - a Segmentation fault when runing samples of xalan-j_2_2_D9

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

DO NOT REPLY [Bug 3728] - TransformerIdentityImpl.transform(src, res) creates a new SAX parser everytime (makes it too 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_bu

DO NOT REPLY [Bug 3728] New: - TransformerIdentityImpl.transform(src, res) creates a new SAX parser everytime (makes it too 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_bu

RE: Result Tree Fragments and Nodesets

And you'll need to put or call Thanks, Dmitry -Original Message- From: Voytenko, Dimitry [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 19, 2001 12:07 To: '[EMAIL PROTECTED]' Subject: RE: Result Tree Fragments and Nodesets Hi Chris, I don't think it's a bug. I

RE: Result Tree Fragments and Nodesets

Hi Chris, I don't think it's a bug. In your XSLT Would have only text-nodes, so xalan:nodeset($group)/data doesn't exist Try to replace xsl:value-of with xsl:copy-of, which copies element nodes Thanks, Dmit

Result Tree Fragments and Nodesets

I am having a problem with RTFs that I don't understand and was wondering if someone can confirm or deny that it is a bug (in D10 at least). I can't get to any of the nodes in a RTF using xsl:value-of, but I can using apply-templates. In the following example, I set a variable with the fragme

cvs commit: xml-xalan/java/src/org/apache/xalan/xsltc/compiler LastCall.java ParameterRef.java PositionCall.java Predicate.java RoundCall.java VariableRefBase.java

morten 01/09/19 10:54:15 Modified:java/src/org/apache/xalan/xsltc/compiler LastCall.java ParameterRef.java PositionCall.java Predicate.java RoundCall.java VariableRefBase.java Log: Fix for combination of wildcards and position predica

DO NOT REPLY [Bug 2332] - TransformerFactoryImpl.getAttribute() is not implemented

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/src/org/apache/xalan/processor TransformerFactoryImpl.java

mmidy 01/09/19 10:41:38 Modified:java/src/org/apache/xalan/processor TransformerFactoryImpl.java Log: Bugzilla 2332: Implement getAttribute() method to return the values for incremental and optimize Revision ChangesPath 1.40 +6 -3 xm

cvs commit: xml-xalan/test/tests/conf-gold/impincl impincl12.out

dmarston01/09/19 10:40:25 Removed: test/tests/conf-gold/impincl impincl12.out Log: This test has been eliminated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: xml-xalan/test/tests/conf/impincl impincl12.xml

dmarston01/09/19 10:39:58 Removed: test/tests/conf/impincl impincl12.xml Log: This test has been eliminated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: xml-xalan/test/tests/conf/mdocs terms.xml

dmarston01/09/19 10:25:37 Modified:test/tests/conf/mdocs terms.xml Log: Improve comments Revision ChangesPath 1.2 +2 -0 xml-xalan/test/tests/conf/mdocs/terms.xml Index: terms.xml === RCS

cvs commit: xml-xalan/test/tests/conf/axes axes112.xsl axes01.xsl

dmarston01/09/19 10:25:07 Modified:test/tests/conf/axes axes112.xsl axes01.xsl Log: Improve comments Revision ChangesPath 1.3 +5 -5 xml-xalan/test/tests/conf/axes/axes112.xsl Index: axes112.xsl ===

cvs commit: xml-xalan/c/Tests/Harness FileUtility.cpp

pauldick01/09/19 10:17:44 Modified:c/Tests/Harness FileUtility.cpp Log: Output number of missing gold files. Domcompare was not detecting additional child nodes in result. Updated text comparison routine to detect missing gold files. Revision ChangesPath 1.14 +

cvs commit: xml-xalan/c/Tests/Harness FileUtility.hpp

pauldick01/09/19 10:14:29 Modified:c/Tests/Harness FileUtility.hpp Log: Added variable to track missing gold files. Revision ChangesPath 1.11 +2 -1 xml-xalan/c/Tests/Harness/FileUtility.hpp Index: FileUtility.hpp =

DO NOT REPLY [Bug 1887] - setURIResolver method not work with Trnsformer

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/src/org/apache/xalan/xsltc/compiler VariableRef.java

morten 01/09/19 09:29:37 Modified:java/src/org/apache/xalan/xsltc/compiler VariableRef.java Log: Forgot to add this file with my fix for bug 1430. PR: bugzilla 1430 Obtained from:n/a Submitted by: [EMAIL PROTECTED] Reviewed by: [EMAIL PROTECTED] Revi

cvs commit: xml-xalan/test/tests/conf-gold/string string139.out string137.out string138.out string136.out

dmarston01/09/19 09:28:52 Added: test/tests/conf-gold/string string139.out string137.out string138.out string136.out Log: More coverage of the translate() function. Revision ChangesPath 1.1 xml-xalan/test/tests/conf-gold/string/

cvs commit: xml-xalan/test/tests/conf/string string139.xsl string136.xsl string137.xml string137.xsl string138.xml string138.xsl string139.xml string136.xml

dmarston01/09/19 09:26:35 Added: test/tests/conf/string string139.xsl string136.xsl string137.xml string137.xsl string138.xml string138.xsl string139.xml string136.xml Log: More coverage of the translate() function. Revision Ch

DO NOT REPLY [Bug 2425] - document() method accesses URIResolver multiple times

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/c/src/Include GCCDefinitions.hpp

dbertoni01/09/19 09:03:52 Modified:c/src/Include GCCDefinitions.hpp Log: One more try... Revision ChangesPath 1.21 +1 -1 xml-xalan/c/src/Include/GCCDefinitions.hpp Index: GCCDefinitions.hpp

cvs commit: xml-xalan/java/src/org/apache/xalan/xsltc/dom BitArray.java DupFilterIterator.java KeyIndex.java

morten 01/09/19 08:53:42 Modified:java/src/org/apache/xalan/xsltc/dom BitArray.java DupFilterIterator.java KeyIndex.java Log: A fix in the duplicate filter iterator to ensure that the iterator can be reset properly. The iterator was using its own variable

DO NOT REPLY [Bug 3254] - Unimplemented interface method error

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/c/src/Include GCCDefinitions.hpp

dbertoni01/09/19 08:33:42 Modified:c/src/Include GCCDefinitions.hpp Log: Fixed endian-ness defines. Revision ChangesPath 1.20 +4 -0 xml-xalan/c/src/Include/GCCDefinitions.hpp Index: GCCDefinitions.hpp =

DO NOT REPLY [Bug 3099] - output type html turn off by included file

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

DO NOT REPLY [Bug 3664] - xalan doesn't appear to support simplified stylesheets

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

DO NOT REPLY [Bug 2754] - xsltc fails conf test impincl14 using default built-in template in addtion to imported template

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

DO NOT REPLY [Bug 3401] - xsltc fails conf tests match17-26 on compound predicates

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

DO NOT REPLY [Bug 3349] - Wildcard in xpath sometimes skips nodes.

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

DO NOT REPLY [Bug 3324] - parameter with '.' in name loses status as node set.

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

DO NOT REPLY [Bug 3311] - not retrieving correct values when wildcard is use with position()

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

DO NOT REPLY [Bug 3238] - context dependent initialization problems with xpaths

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

DO NOT REPLY [Bug 2954] - xsltc fails output25

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

DO NOT REPLY [Bug 2952] - xsltc fails conf test output24

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

DO NOT REPLY [Bug 2607] - xsltc fails embed03 and 04 missing the xml declaration and data

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

DO NOT REPLY [Bug 3722] New: - Accessing NodeList getChildNodes() in extension function throws DTMDOMException

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

RE: Extension Function Problem/Incompatible DocumentFragmentImpl implementations?

The core issue behind this bug relates to some type of internal difference between the results of a select and a copy-of relative to variable assignment. The following works with our extension function, and, as expected passed a properly populated NodeList to the extension function: The follo

Re: DTMDOMException

Christian, Can you please enter this as a bug ( at http://nagoya.apache.org/bugzilla)? It will be better tracked if you do. Thanks! Myriam Christian Haul

DO NOT REPLY [Bug 3314] - xsltc fails conf test axes117 expecting to find object/array on stack

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/src/org/apache/xalan/xsltc/dom DOMImpl.java MatchingIterator.java StepIterator.java

morten 01/09/19 06:22:51 Modified:java/src/org/apache/xalan/xsltc/dom DOMImpl.java MatchingIterator.java StepIterator.java Log: Verious fixes for iterators. PR: n/a Obtained from:n/a Submitted by: [EMAIL PROTECTED] Reviewed by: [EM

DO NOT REPLY [Bug 2581] - xsltc fails conf tests conditional13,14, and 15

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

DO NOT REPLY [Bug 3688] - xsltc differs from Xalan on conf test whitespace23

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

DO NOT REPLY [Bug 3314] - xsltc fails conf test axes116 expecting to find object/array on stack

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

DO NOT REPLY [Bug 3267] - xsltc compiler fails silently when xslt references bogus template

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

DO NOT REPLY [Bug 2583] - xsltc fails conf tests conflictres22 and 23 with predicates in match patterns

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

DO NOT REPLY [Bug 2582] - xsltc fails conflictres19 and 20 on namespace vs non-namespaced elements

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

Re: the Translet API and TRaX

Todd, I believe that you inadvertently put the wrong e-mail address in the following message.  My name is Jim Vose, and I have recently joined the Xalan mailing list to follow the development of the Xalan-J, and become more familiar with it. Just wanted to let you know so you could forward the mes

cvs commit: xml-xalan/java/src/org/apache/xalan/xsltc/runtime DefaultSAXOutputHandler.java TextOutput.java

morten 01/09/19 05:08:26 Modified:java/src/org/apache/xalan/xsltc/runtime DefaultSAXOutputHandler.java TextOutput.java Log: Modified the output handler and SAX handler to produce proper HTML output. Special characters in

DO NOT REPLY [Bug 1498] - XSLTMark benchmark test 'xpath' has missing output

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/src/org/apache/xalan/xsltc/compiler Predicate.java StepPattern.java TestSeq.java

morten 01/09/19 04:50:31 Modified:java/src/org/apache/xalan/xsltc/compiler Predicate.java StepPattern.java TestSeq.java Log: Fix for predicates used in complex match patterns. The compiler failed to produce code that would match on patterns like "blob/*[@a

Re: the Translet API and TRaX

Dean, Thanks for the interest in our XSLTC efforts. Improvements are made to the codebase everyday. To get the latest code, you can access our CVS source tree at the page: http://xml.apache.org/cvs.html XSLTC is under the module 'xml-xalan'. To see what needs to be done,

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

morten 01/09/19 04:39:41 Modified:java/src/org/apache/xalan/xsltc TransletException.java Log: Changed the TransletException class so that it inherits from SAXException and not from Exception. This should make it possible for us to avoid testing for both SAXExceptions and Transl

Re: Problem with the XSLTC.class in public void outputToJar() throwsIOException

Shocking! The 'MANIFEST_VERSION' attribute is in the Java 1.2 spec, so it seems the JVM VA is using is not 100% compliant. Thank you for bringing this ot my attention. I will implement a little fix to get around this problem. Morten Jorgensen XML Technology Center Sun Microsystems [EMAIL PROTECT

DTMDOMException

Hi. When accessing child nodes in a NodeList passed to an extension function an DTMDOMException is thrown. [foo.xsl] [/foo.xsl]

DO NOT REPLY [Bug 3714] New: - java.lang.StackOverflowError on docbook document

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