DO NOT REPLY [Bug 13550] - Elements not output using CDATA, but CDATA was requested

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 13550] New: - Elements output using CDATA, but CDATA was not requested

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 13548] New: - EBCDIC encoding not working with XSLTC

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

cvs commit: xml-xalan/java/src/org/apache/xpath/axes InterceptPathIterator.java

mmidy 2002/10/11 12:38:21 Removed: java/src/org/apache/xpath/axes Tag: xslt20 InterceptPathIterator.java Log: remove from source - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional

cvs commit: xml-xalan/java/src/org/apache/xml/dtm/dom2dtm2 DOM2DTM2Base.java

mmidy 2002/10/11 10:53:15 Modified:java/src/org/apache/xml/dtm/dom2dtm2 Tag: xslt20 DOM2DTM2Base.java Log: implement getElementByIdref Revision ChangesPath No revision No revision 1.1.2.2 +7

SQL Extension enhancement/replacement

Title: SQL Extension enhancement/replacement I have been working on an enhanced SQL extension for Xalan-J. This adds support for callable statements, multiple result sets, and output parameters. To do this it makes some changes from the syntax of the existing SQL extension. Most significantly

Re: Problem when input document contains attribute xmlns

XSLT does not support non-namespace-aware processing. If that's what you want, you need another tool. Sorry, but XML 1.0 without namespaces is pretty much deprecated at this point. __ Joe Kesselman / IBM Research

Re: Problem when input document contains attribute xmlns

Joseph Kesselman wrote: > An attribute called xmlns declares the default namespace for that element > and its descendents. See the namespaces spec. > > __ > Joe Kesselman / IBM Research In reply to my own: >> In this particular context, its not a namespace,

Re: Problem when input document contains attribute xmlns

An attribute called xmlns declares the default namespace for that element and its descendents. See the namespaces spec. __ Joe Kesselman / IBM Research

Re: Problem when input document contains attribute xmlns

Joseph Kesselman wrote: > This is a FAQ. > > XSLT is namespace-sensitive. If you specify a namespace in your source > document you _must_ use that namespace when your stylesheet attempts to > check the node's names, or the match will fail. XSLT 1.0 has no concept of > default namespace in sele

Re: can Xalan be compiled under JDK 1.4.x?

An alternative solution is to fix the dependency of the first batch on the second batch. The files under org.apache.xml are in the first javac batch. They have dependencies on files under org.apache.xalan which are in the second javac batch. We faced the same problem in the packaging issue for the

Re: Problem when input document contains attribute xmlns

This is a FAQ. XSLT is namespace-sensitive. If you specify a namespace in your source document you _must_ use that namespace when your stylesheet attempts to check the node's names, or the match will fail. XSLT 1.0 has no concept of default namespace in select or match patterns, so within the

Problem when input document contains attribute xmlns

I would much appreciate any help with the following problem. I am pretty new to XSL, so I may have screwed something up. Using the following stylesheet: http://www.w3.org/1999/XSL/Transform";> The following input document will not generate any output: http://twister

cvs commit: xml-xalan/test/tests/conf-gold/lre lre09.out

dmarston2002/10/11 08:39:27 Modified:test/tests/conf-gold/lre lre09.out Log: Totally new LRE09, covering name characters and casing. Revision ChangesPath 1.3 +1 -12 xml-xalan/test/tests/conf-gold/lre/lre09.out Index: lre09.out ===

cvs commit: xml-xalan/test/tests/conf/lre lre09.xsl lre09.xml

dmarston2002/10/11 08:37:10 Added: test/tests/conf/lre lre09.xsl lre09.xml Log: Totally new LRE09, covering name characters and casing. Revision ChangesPath 1.3 +9 -27 xml-xalan/test/tests/conf/lre/lre09.xsl 1.3 +2 -5 xml-xalan/test/t

DO NOT REPLY [Bug 13534] - Cannot access any attributes, if node is returned from extension functíon

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

cvs commit: xml-xalan/test ibmjdk118.test.properties ibmjdk122.test.properties jdk118.test.properties

mkwan 2002/10/11 08:11:30 Added: test ibmjdk118.test.properties ibmjdk122.test.properties Removed: test jdk118.test.properties Log: Rename jdk118.test.properties to ibmjdk118.test.properties. Add a new file ibmjdk122.test.properties for excluded testcase in IBM

Re: can Xalan be compiled under JDK 1.4.x?

I just checked and found that compilation under JDK 1.1.8 is already broken. There are a lot of errors with messages like " Cyclic class inheritance or scoping". This is exactly the same error the workaround of separating the build into three batches was supposed to fix. I think this workaround is

Re: can Xalan be compiled under JDK 1.4.x?

I thought that Sun and IBM were dropping support for the 1.1.x JDK. If that is so I would think that it would be ok to drop support for 1.1.x some time after that support is dropped. (e.g. don't support 1.1.8 six months after support for 1.1.8 is dropped) Claude Joseph Kesselman wrote: > La

DO NOT REPLY [Bug 13535] New: - Cannot access any attributes, if node is returned from extension functíon

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 13534] New: - Cannot access any attributes, if node is returned from extension functíon

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: can Xalan be compiled under JDK 1.4.x?

Last I checked, we still have some users who claim _their_ users can't upgrade from 1.1.8. Being able to compile against that version is still part of our official spec. I'd love to drop it, but I don't think that's on the table yet. On the other hand, it might not be unreasonable to have a se

Re: can Xalan be compiled under JDK 1.4.x?

I've confirmed that compiling all the java files for Xalan in one batch works correctly with Sun JDK 1.4.0. Actually the files in the first batch have dependencies on the files in the second batch. I think that is why the Xalan classes in rt.jar are referenced. The reason for the batch separation

DO NOT REPLY [Bug 13534] - Cannot access any attributes, if node is returned from extension functíon

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 13534] - Cannot access any attributes, if node is returned from extension functíon

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 13535] - Cannot access any attributes, if node is returned from extension functíon

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