Re: fail to gmake on AIX, TOO!

What Xalan version and source package are you using? Dave [EMAIL PROTECTED] yu.edu

fail to gmake on AIX, TOO!

Hi, Everyone, thanks for answer my question about failure to make C version of xalan on AIX. (see the email I sent to the e-grp yesterday). Someone suggested me to use gmake. I tried too, but failed too. In fact, gmake is installed on AIX, version 3.77. My commands are: $ runConfigure -p ai

cvs commit: xml-xalan/c/src/XPath XObject.cpp

dbertoni01/11/16 16:12:59 Modified:c/src/XPath XObject.cpp Log: More efficient comparisons of strings. Make sure strings are compared properly. Revision ChangesPath 1.27 +213 -9xml-xalan/c/src/XPath/XObject.cpp Index: XObject.cpp

DO NOT REPLY [Bug 4908] - XPath's text() and node() selectors get confused by CDATA sections

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 4908] - XPath's text() and node() selectors get confused by CDATA sections

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/Tests/Conf conf.cpp

pauldick01/11/16 13:25:11 Modified:c/Tests/Conf conf.cpp Log: Changed signature of analyzeResults Revision ChangesPath 1.9 +1 -1 xml-xalan/c/Tests/Conf/conf.cpp Index: conf.cpp === RCS fi

cvs commit: xml-xalan/c/Tests/Extensions extensions.cpp

pauldick01/11/16 13:24:02 Modified:c/Tests/Extensions extensions.cpp Log: Changed signature of analyzeResults and output test specific result files Revision ChangesPath 1.12 +15 -14xml-xalan/c/Tests/Extensions/extensions.cpp Index: extensions.cpp ==

cvs commit: xml-xalan/c/Tests/Params Params.cpp

pauldick01/11/16 13:22:14 Modified:c/Tests/Params Params.cpp Log: Changed signature of analyzeResults Revision ChangesPath 1.14 +2 -1 xml-xalan/c/Tests/Params/Params.cpp Index: Params.cpp ==

cvs commit: xml-xalan/c/Tests/InputSource inputsource.cpp

pauldick01/11/16 13:21:45 Modified:c/Tests/InputSource inputsource.cpp Log: Changed signature of analyzeResults and added test for XercesDOMWrapperParsedSource Revision ChangesPath 1.8 +41 -2 xml-xalan/c/Tests/InputSource/inputsource.cpp Index: inputsou

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

pauldick01/11/16 13:20:30 Modified:c/Tests/Harness FileUtility.cpp FileUtility.hpp Log: Changed signature of analyzeResults Revision ChangesPath 1.23 +10 -6 xml-xalan/c/Tests/Harness/FileUtility.cpp Index: FileUtility.cpp =

cvs commit: xml-xalan/test/tests/extensions/library libraryNodeset01.xsl libraryNodeset03.xsl

pauldick01/11/16 13:15:03 Modified:test/tests/extensions/library libraryNodeset01.xsl libraryNodeset03.xsl Log: Minor changes Revision ChangesPath 1.3 +3 -15 xml-xalan/test/tests/extensions/library/libraryNodeset01.xsl Index: librar

cvs commit: xml-xalan/test/tests/extensions-gold/library libraryNodeset01.out libraryNodeset03.out

pauldick01/11/16 13:14:50 Modified:test/tests/extensions-gold/library libraryNodeset01.out libraryNodeset03.out Log: Minor changes Revision ChangesPath 1.3 +1 -22 xml-xalan/test/tests/extensions-gold/library/libraryNodeset01.out In

Re: Need help - please advise about following error message, thanks

You don't have Xalan properly set up in your classpath.  Try copying xalan.jar to either /WEB-INF/lib/xalan.jar (preferred) or $TOMCAT_HOME/lib/xalan.jar, restart Tomcat, and try again. [EMAIL PROTECTED] wrote: [EMAIL PROTECTED]"> Error: 500 Location: /eneuwirth01/servlet/disp

Re: xsl:strip-space bug?

There's a sample "identity transform" in the XSLT spec. Swipe that, add your strip-space request, and see how that works for you...

Re: xalan:evaluate( XPath - expression ) help needed......

Hi Atul, This is the result of a limitation of defining literals in XPath. Using entities such as ', won't change how a literal is interpreted, since the XML parser resolves the entities before the XSLT processor sees the attribute. Thus, your expression looks like this to the XSLT processor:

Re: How to provide the data while parsing errors through the exception

Xalan relies on Xerces -- or another JAXP-compliant parser -- to parse the input file. If that parser attempts to recover, we recover; if it doesn't, we don't. Very few will. An ill-formed XML file is simply Not An XML File. I'd suggest you try to get whoever's running your server to rewrite the

DO NOT REPLY [Bug 4908] - XPath's text() and node() selectors get confused by CDATA sections

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: xalan:evaluate( XPath - expression ) help needed......

The problem is that the ' are being expanded to a single quote, which is interpreted the exact same as the other single quotes that are deliminating the string. The ' only escapes the single quote inside of the select="..." attribute -- it does not perform any escaping on the XPath string lit

Re: xsl:strip-space bug?

Anamitra, This is the mailing list for Xalan related discussion. The stylesheet you presented does nothing. You've defined no templates so the default template is executing, with the correct output. Add some templates and you should start to see thing happen. Paul

Need help - please advise about following error message, thanks

Error: 500 Location: /eneuwirth01/servlet/displayhtml Internal Servlet Error: javax.xml.transform.TransformerFactoryConfigurationError: Provider for javax.xml.transform.TransformerFactory cannot be found at javax.xml.transform.TransformerFactory.newInstance(TransformerFactory.java:145) at XS

xsl:strip-space bug?

Hi all I am trying to write an xsl script which strips all those elements in the input xml files which contails white space as their values - and thought of using this simple script - http://www.w3.org/1999/XSL/Transform"; version ="1.0"> But when I run it on xalan transformer I get only the

CAPI extensions

Hi there. I'm relativly new to Xalan (and a complete novice with C++!!). We have a UNIX based product which used a C API to interface to the outside world. While implementing an XML interface using Xalan/Xerces I wanted to avoid the use of files completely and so have exposed some more of the

How to provide the data while parsing errors through the exception

Hi, we have the above problem. If during parsing an error occurs, It would be useful for diagnostic purposes to show the user the wrong data. For example we use a proxy, and when the requested xsl file does not exist, the proxy generates an error document in HTML, which is of course not parseable

[BUG?]: Threading Problem with Xalan and Incremental Processing

Hi, we are here experiencing problems with Cocoon 2 and Xalan when we turn on the incremental processing of Xalan. The environment is Windows 2K, JDK 1.3.1, Tomcat 3.3, Xerces 1.4.3. The problem occurs with the latest Cocoon 2 RC2 and the current version of Xalan used in the RC2 (D5 or D6?) an

xalan:evaluate( XPath - expression ) help needed......

I have the following stylesheet: http://www.w3.org/1999/XSL/Transform" xmlns:xalan="http://xml.apache.org/xalan" version="1.0"> Where I am using xalan:evaluate extension function. // Works Fine Starts --

cvs commit: xml-xalan/c/src/XPath XPathProcessorImpl.cpp

dbertoni01/11/16 11:34:22 Modified:c/src/XPath XPathProcessorImpl.cpp Log: Check to see that a prefix has been bound to a valid namespace URI. Revision ChangesPath 1.45 +16 -14xml-xalan/c/src/XPath/XPathProcessorImpl.cpp Index: XPathProcessorImpl.cpp

DO NOT REPLY [Bug 4912] - Incremental Processing blocks

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 4912] - Incremental Processing blocks

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 4908] - XPath's text() and node() selectors get confused by CDATA sections

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 4908] - XPath's text() and node() selectors get confused by CDATA sections

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 4906] - xsltc ingoring the standalone="no" attribute in output method

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 4906] - xsltc ingoring the standalone="no" attribute in output method

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/runtime AbstractTranslet.java

tmiller 01/11/16 09:31:16 Modified:java/src/org/apache/xalan/xsltc/runtime AbstractTranslet.java Log: bug fix 4906 Revision ChangesPath 1.29 +2 -2 xml-xalan/java/src/org/apache/xalan/xsltc/runtime/AbstractTranslet.java Index: Abstr

DO NOT REPLY [Bug 4906] - xsltc ingoring the standalone="no" attribute in output method

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: new comer:fail to make on AIX

Read the FAQ -- You need GNU make. Dave [EMAIL PROTECTED] yu.edu To: [EMAIL

Re: Xalan 2.2 Memory Usage

Is there a simple way to turn off the cacheing at the API level for testing purposes so I can see if the memory problems go away?  At least I would know if that was the problem or not and could go from there. Chris [EMAIL PROTECTED] wrote: [EMAIL PROTECTED]"> On Friday, 11/16/2001 at 10:11 C

DO NOT REPLY [Bug 3686] - xsltc fails conf test whitespace13

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 4912] - Incremental Processing blocks

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 4912] - Incremental Processing blocks

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: Automatic response content-type

Kai Ojansu writes (excerpted): >...is there going to be some kind >of xalan:content-type attribute in future versions of Xalan? >...In my point of view (hope I'm not lost), stylesheet's output rarely >can have (I can't think of any) multiple content-types. The XSL Working Group of the W3C is lik

Re: Xalan 2.2 Memory Usage

On Friday, 11/16/2001 at 10:11 CET, Claudio Sacerdoti Coen <[EMAIL PROTECTED]> wrote: > be possible to have the PI extended also to the case of > document() in head position inside the select of a xsl:copy-of? We know we need a general answer to the question of DTM cache control -- preferably

DO NOT REPLY [Bug 4908] - XPath's text() and node() selectors get confused by CDATA sections

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: Xalan 2.2 Memory Usage

On Thursday, 11/15/2001 at 04:52 MST, "Chris McCabe" <[EMAIL PROTECTED]> wrote: > If we load the > same documents over and over, would we see increasing memory > consumption, or does it reuse the cached version? It's supposed to reuse. But if you're having memory use problems, we should check th

DO NOT REPLY [Bug 4921] - xsltc regressed on the rahtz6 test on Nov 2

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 4921] New: - xsltc regressed on the rahtz6 test on Nov 2

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

[GUMP] Xalan2 Smoketest Failure

This email is autogenerated from the output from: Build results exceed maximum length.Please see URL above for det

Automatic response content-type

Xalan has some own output properties, but is there going to be some kind of xalan:content-type -attribute in future versions of Xalan? It would also need some kind of new interface in Transformer (tr.transform(domSource,httpResponse)). In my point of view (hope I'm not lost), stylesheet's output

DO NOT REPLY [Bug 4912] New: - Incremental Processing blocks

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: Xalan 2.2 Memory Usage

> If you're using document() heavily, there are some known issues regarding > whether/when/how-long a DTM is retained in memory. There's a PI that can be > used as a workaround in the common case of an with a > document()-based expression in its select, but a general and automated > answer is sti