DO NOT REPLY [Bug 3357] - bug in 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 2835] - Redirecting problems with variables and parameters

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 4533] - strange mixing of param-value

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 4989] New: - Null pointer in TransformerFactory.newInstance() when jaxp.properties is present.

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 4987] New: - apply-imports needs to be more careful in default case

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 dependent on Xerces?

>Let me restate so I'm clear on what's going on, and hopefully others will >be too: Close... At this time there really are some compile-time dependencies on Xerces. Most of them are in a class which is only used with Xerces, so if that class fails to compile it's ugly but isn't a problem for fo

Re: Xalan dependent on Xerces?

you [EMAIL PROTECTED] wrote > There are currently some compile-time dependencies. There shouldn't be any > runtime dependencies. Let me restate so I'm clear on what's going on, and hopefully others will be too: In Xalan There are currently some optional compile-time dependencies. There

RE: Line endings translation problem

Hi Brian, Any output sent to stderr is sent through embedded strings with std::endl, so it's living in the world of C/C++ text-mode streams. Since that's the case, it's always consistent and we don't care that the platform is translating \n to \r\n. Serialized XML is a different beast. We try

RE: Line endings translation problem

Thanks for the reply, Dave. I didn't believe you about it working with files but you're right :-) Since, as you say, the XML is normalized to '\n', I was suprised that there were '\r's being passed to XalanOutputStream. Maybe the platform line ending conversion is happening too early in the proc

Re: Line endings translation problem

This is a really difficult problem to deal with when writing to stdout/cout. Since XML normalizes everything to \n, we end up having to normalize back to \r\n on Windows. Sometimes we can do it, and sometimes we can't. When writing to a binary file, it's not a problem, since we always open fil

Line endings translation problem

Hi, I couldn't find a bug filed against problem this so I thought I'd ask the group if anyone has encountered before. I'm using Xalan 1.1/Xerces 1.4. It looks like the problem is that XalanOutputStream is being passed string containing platform line endings in some cases and UNIX line endings in

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

pauldick01/11/20 12:45:17 Modified:c/Tests/InputSource inputsource.cpp Log: Cleanup the code. Revision ChangesPath 1.9 +11 -12xml-xalan/c/Tests/InputSource/inputsource.cpp Index: inputsource.cpp ===

Re: Xalan dependent on Xerces?

There are currently some compile-time dependencies. There shouldn't be any runtime dependencies. The IncrementalSAXSource_Xerces class requires that xerces.jar be present at compile time... but if that fails to compile, no harm is done unless you later want to leverage Xerces after all; we can f

DO NOT REPLY [Bug 4498] - Xalan doesn't build on Solaris 8 (C++ 5.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

cvs commit: xml-xalan/c/src/XercesParserLiaison XercesBridgeNavigator.cpp

pauldick01/11/20 12:14:11 Modified:c/src/XercesParserLiaison XercesBridgeNavigator.cpp Log: Fixed test for checking if parent element is already known. Revision ChangesPath 1.7 +1 -1 xml-xalan/c/src/XercesParserLiaison/XercesBridgeNavigator.cpp Index: Xer

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

dbertoni01/11/20 12:05:16 Modified:c/src/XalanSourceTree FormatterToSourceTree.cpp Log: Fixed bug with handling of whitespace in document fragments. Revision ChangesPath 1.11 +3 -1 xml-xalan/c/src/XalanSourceTree/FormatterToSourceTree.cpp Index: FormatterT

DO NOT REPLY [Bug 4983] New: - xsltc applies default namespace to both output elements in conf test namespace105

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

Xalan dependent on Xerces?

Quick question on xerces.jar and Xalan: In xml-xalan/java/src/org/apache/xml/dtm/ref, there are several dependencies on xerces, and therefore building xalan seems to require 'xerces.jar' to be available to the build process. Is 'xerces.jar' required to build Xalan? Grep for 'xerces' in that dir

cvs commit: xml-xalan/c/src/XercesParserLiaison XercesBridgeNavigator.cpp

pauldick01/11/20 07:54:21 Modified:c/src/XercesParserLiaison XercesBridgeNavigator.cpp Log: Return parent element if already know Revision ChangesPath 1.6 +15 -2 xml-xalan/c/src/XercesParserLiaison/XercesBridgeNavigator.cpp Index: XercesBridgeNavigator.cpp

Re: Compiler warnings

Thanks for your reply. Reassuring to know nothing major's wrong! Richard. - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, November 20, 2001 3:33 PM Subject: Re: Compiler warnings > > It's Dinkumare's/Microsoft's sloppy library code that's the pro

Xalan not loading under VB

We have a MSVC++ dll that uses the Xalan and Xerces dlls to generate and transform an XML document. Under our main program this all works lovely :- A Delphi front-end implicitly loads up a controlling DLL. This DLL then uses LoadLibrary to load the XML generator DLL, which in turns implici

Re: Compiler warnings

It's Dinkumare's/Microsoft's sloppy library code that's the problem -- you can ignore the warnings. We keep them at that level so we can detect any problems from the Xalan code. In the last beta of VC++ 7, Dinkumware seems to have cleaned up their act, and there are no warnings from the library

Re: can xalan works concurrently? (about the example)

Xalan does not do parallel processing of a single transform. That could be interesting for certain transformations when the processor can determine that things can be done out-of-sequence, but it would still need to re-assemble the pieces in sequence. That's a great research topic, but I don't

Compiler warnings

Hi   I'm trying to compile the SimpleXPathAPI sample project that came with Xalan-C 1.2 (the latest version I could find on xml.apache.org) in Visual C++ 6 Pro, SP5, with the mods listed on the Dinkumware web pages.   First time I build it (straight out of the zip file, only change to make t

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

morten 01/11/20 05:55:21 Modified:java/src/org/apache/xalan/xsltc/compiler Sort.java Log: Fix for a big in the implementation. The element would not always work properly in the innermost loop in nested elements. PR: bugzilla 4921 Obtained from:n/a Submit

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 4962] - Typo in constructor DOM2DTM$defaultNamespaceDeclarationNode

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/xml/dtm/ref/dom2dtm DOM2DTM.java

jkesselm01/11/20 05:46:51 Modified:java/src/org/apache/xml/dtm/ref/dom2dtm DOM2DTM.java Log: "Tupograflica eror". Sorry 'bout that! Revision ChangesPath 1.21 +9 -18 xml-xalan/java/src/org/apache/xml/dtm/ref/dom2dtm/DOM2DTM.java Index: DOM2DTM.java ===

cvs commit: xml-xalan/java/src/org/apache/xalan/xsltc/compiler Mode.java Template.java xpath.cup

morten 01/11/20 05:32:01 Modified:java/src/org/apache/xalan/xsltc/compiler Mode.java Template.java xpath.cup Log: Fix for nested parent location paths / filter parent paths with key() or id() root. These paths would in some case returnt he root node when t

DO NOT REPLY [Bug 4781] - xsltc selecting node not specified by key

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