Re: Transforming memory grows (Xalan-C)

>At any rate, it's _always_ more efficient to avoid the creation of result >tree fragments, so you should always use this: > > > >instead of this: > > > > > >whenever you can. This is not a "special" use of xsl:with-param. Ok, "special" was the wrong term. I meant "another". >By the way,

DO NOT REPLY [Bug 7556] - Memory grows while transforming

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/PlatformSupport XSLException.cpp XSLException.hpp

dbertoni02/03/27 23:10:18 Modified:c/src/PlatformSupport XSLException.cpp XSLException.hpp Log: Added default error formatting. Revision ChangesPath 1.6 +91 -0 xml-xalan/c/src/PlatformSupport/XSLException.cpp Index: XSLException.cpp =

cvs commit: xml-xalan/c/src/PlatformSupport DoubleSupport.cpp

dbertoni02/03/27 23:09:49 Modified:c/src/PlatformSupport DoubleSupport.cpp Log: Make sure we do floating-point modulus when necessary. Revision ChangesPath 1.30 +13 -1 xml-xalan/c/src/PlatformSupport/DoubleSupport.cpp Index: DoubleSupport.cpp

cvs commit: xml-xalan/c/src/Include HPUXDefinitions.hpp

dbertoni02/03/27 23:09:30 Modified:c/src/Include HPUXDefinitions.hpp Log: Put back #define. Revision ChangesPath 1.11 +2 -1 xml-xalan/c/src/Include/HPUXDefinitions.hpp Index: HPUXDefinitions.hpp ===

cvs commit: xml-xalan/c/src/XalanTransformer XercesDOMWrapperParsedSource.cpp

dbertoni02/03/27 23:09:11 Modified:c/src/XalanTransformer XercesDOMWrapperParsedSource.cpp Log: Destroy the wrapper document in the destructor. Revision ChangesPath 1.4 +1 -0 xml-xalan/c/src/XalanTransformer/XercesDOMWrapperParsedSource.cpp Index: Xerces

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

dbertoni02/03/27 23:08:47 Modified:c/src/XalanTransformer XalanTransformer.cpp Log: Unload ICU functions and extension functions in terminate(). Revision ChangesPath 1.45 +31 -0 xml-xalan/c/src/XalanTransformer/XalanTransformer.cpp Index: XalanTransformer.c

cvs commit: xml-xalan/c/src/XSLT ElemAttributeSet.cpp

dbertoni02/03/27 23:08:05 Modified:c/src/XSLT ElemAttributeSet.cpp Log: Cleaned-up unused map. Improved result namespace handling. Revision ChangesPath 1.18 +1 -1 xml-xalan/c/src/XSLT/ElemAttributeSet.cpp Index: ElemAttributeSet.cpp

cvs commit: xml-xalan/c/src/XSLT XSLTEngineImpl.cpp XSLTEngineImpl.hpp

dbertoni02/03/27 23:07:57 Modified:c/src/XSLT XSLTEngineImpl.cpp XSLTEngineImpl.hpp Log: Cleaned-up unused map. Improved result namespace handling. Revision ChangesPath 1.136 +35 -57xml-xalan/c/src/XSLT/XSLTEngineImpl.cpp Index: XSLTEngineImpl.cpp ===

DO NOT REPLY [Bug 7556] New: - Memory grows while transforming

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 StylesheetHandler.cpp

dbertoni02/03/27 20:55:39 Modified:c/src/XSLT StylesheetHandler.cpp Log: Disallow top-level elements with a null namespace URI. Revision ChangesPath 1.76 +15 -4 xml-xalan/c/src/XSLT/StylesheetHandler.cpp Index: StylesheetHandler.cpp ==

cvs commit: xml-xalan/c/src/XSLT XalanSourceTreeDocumentFragmentAllocator.hpp

dbertoni02/03/27 20:52:27 Modified:c/src/XSLT XalanSourceTreeDocumentFragmentAllocator.hpp Log: Fixed documentation. Revision ChangesPath 1.2 +5 -5 xml-xalan/c/src/XSLT/XalanSourceTreeDocumentFragmentAllocator.hpp Index: XalanSourceTreeDocumentFragmentAl

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

dbertoni02/03/27 20:17:09 Modified:c/src/XPath ElementPrefixResolverProxy.cpp Log: Commented out unused parameter. Revision ChangesPath 1.8 +1 -1 xml-xalan/c/src/XPath/ElementPrefixResolverProxy.cpp Index: ElementPrefixResolverProxy.cpp

cvs commit: xml-xalan/test/java/src/org/apache/qetest/xsl StylesheetDatalet.java StylesheetDataletManager.java

curcuru 02/03/27 18:15:34 Modified:test/java/src/org/apache/qetest/xsl StylesheetDatalet.java StylesheetDataletManager.java Log: Fix hole when user-supplied -fileList is passed where -flavor arg wasn't properly passed through to underlying datalets; found b

(SQL Extension / NPE issue) Re: Help, waiting on an answer

Scott, Glad to hear that you are felling better. I was assuming that SQL mods (besides the storm I started with the inclusion of 3rd party jars) just were not making it to the top of the list. The problem at hand. If the SQL Extension runs into a problem, it records the error and returns DTM.NU

cvs commit: xml-xalan/java/src/org/apache/xml/utils SAXSourceLocator.java

sboag 02/03/27 14:15:11 Modified:java/src/org/apache/xml/utils SAXSourceLocator.java Log: Add a constructor that takes a SourceLocator. Revision ChangesPath 1.5 +16 -0 xml-xalan/java/src/org/apache/xml/utils/SAXSourceLocator.java Index: SAXSourceLocator.

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

sboag 02/03/27 14:14:13 Modified:java/src/org/apache/xalan/transformer TransformerImpl.java Log: Fix problem with the SAXSourceLocator not getting the line number info. Revision ChangesPath 1.128 +9 -1 xml-xalan/java/src/org/apache/xalan/transformer/Transform

cvs commit: xml-xalan/java/src/org/apache/xalan/trace PrintTraceListener.java

sboag 02/03/27 14:12:57 Modified:java/src/org/apache/xalan/trace PrintTraceListener.java Log: Handle TraceListenerEx2, even though we don't do anything with the extra methods. Revision ChangesPath 1.13 +57 -2 xml-xalan/java/src/org/apache/xalan/trace/PrintTra

cvs commit: xml-xalan/java/src/org/apache/xalan/trace TraceListenerEx2.java

sboag 02/03/27 14:12:14 Modified:java/src/org/apache/xalan/trace TraceListenerEx2.java Log: Fix JavaDoc comment. Revision ChangesPath 1.2 +1 -1 xml-xalan/java/src/org/apache/xalan/trace/TraceListenerEx2.java Index: TraceListenerEx2.java ==

cvs commit: xml-xalan/java/src/org/apache/xalan/templates ElemApplyTemplates.java

sboag 02/03/27 14:11:32 Modified:java/src/org/apache/xalan/templates ElemApplyTemplates.java Log: Fix Frank Weiss bug, which has to do with the currentFrameBottom not being restored properly when inside a with-param. Fix Cristina bug where the traceEnd event was being passe

Re: How can I serialize my XML doc with an opening and closing tag

Hi Vincent, --On Mittwoch, 27. März 2002 15:53 +0100 "MAHE Vincent FTRD/DIH/REN" <[EMAIL PROTECTED]> wrote: > > I would like to serialize my Document with Xalan but the problem is that > if the element is empty, it serializes it as . > How can I explicitly serialize my node as ? Use Canonica

DO NOT REPLY [Bug 7528] New: - 'preceding-sibling' axis not updating correctly during template processing

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 7524] - Some Documents fail for ApacheModuleXSLT, but not Xalan executable.

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 7524] New: - Some Documents fail for ApacheModuleXSLT, but not Xalan executable.

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 7522] - Missing current-group function

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: Transforming memory grows (Xalan-C)

The converse of what? Speed or memory? Holger's stylesheet creates variables, but one type of variable (a result tree fragment) is much more expensive than another type (a string). It seems a similar situation to me -- creating something is always more expensive than not creating something. In

DO NOT REPLY [Bug 7522] New: - Missing current-group function

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: Transforming memory grows (Xalan-C)

Interesting, the converse seems to be true when using variables. When processing the same stylesheet using: versus The latter approach is SIGNIFICANTLY faster. Any explanation you can think of? Rick Bullotta CTO Lighthammer Software (www.lighthammer.com) -Original Message- From:

RE: StreamSource Question

You should read the section in the recommendation regarding conflicts: http://www.w3.org/TR/xslt#conflict This is one of the cases that is an error, but is recoverable: "It is an error if this leaves more than one matching template rule. An XSLT processor may signal the error; if it does

Re: Transforming memory grows (Xalan-C)

This is definitely due to the creation of result tree fragments. Right now, we use one document as a factory for result tree fragments. That's usually not a problem, but when you create lots of result tree fragments and they have lots of text, that can cause data to grow uncontrollably. At any

RE: StreamSource Question

See the XSLT spec. There are a few very simple rules for what happens when two templates could match the same node, but in my opinion they aren't enough to yield really predictble results in most cases. The right answer involves explicitly assigning priorities to the templates to control how ties

RE: StreamSource Question

Joseph, It turned out this was unrelated. I had a bug in my stylesheet. I would like to clarify my understanding of one point of XSLT: If you have two templates which a given Node can match, it appears that the first one it finds is applied, and then no others (unless they are referred to within

DO NOT REPLY [Bug 6463] - Severe Performance problems (Memory + Time taken) compared to SAXON

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

SQL Extension FilterExprWalker NPE

Good morning, I've already contacted John Gentilin directly about this problem, but I thought I might as well open the question to the list as well. From what I hear, the Xalan-J SQL extension is working except for several NPEs in FilterExprWalker. To quote John: >The only item that fell th

RE: How can I serialize my XML doc with an opening and closing tag

Title: RE: How can I serialize my XML doc with an opening and closing tag thanks, I will build a post-process system. Vincent -Message d'origine- De: Joseph Kesselman/CAM/Lotus [mailto:[EMAIL PROTECTED]] Date: mercredi 27 mars 2002 16:08 À: [EMAIL PROTECTED] Objet: Re: How can I se

Re: Transforming memory grows (Xalan-C)

>In this case you have requested whitespace (line breaks and indentation) >around the value-of's result. This means XSLT has to create the >concatenated data. I'm not sure how Xalan-C s handling that, but in Xalan-J >you might also be creating a Result Tree Fragment to contain the result of >that

Re: Transforming memory grows (Xalan-C)

In this case, you're using the value directly, which should work pretty efficiently. In this case you have requested whitespace (line breaks and indentation) around the value-of's result. This means XSLT has to create the concatenated data. I'm not sur

cvs commit: xml-xalan/c/samples/XPathWrapper XPathWrapper.cpp

dbertoni02/03/27 07:20:11 Modified:c/samples/XPathWrapper XPathWrapper.cpp Log: Fixed typo. Revision ChangesPath 1.16 +1 -1 xml-xalan/c/samples/XPathWrapper/XPathWrapper.cpp Index: XPathWrapper.cpp

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

dbertoni02/03/27 07:17:20 Modified:c/src/XalanTransformer XalanTransformer.cpp Log: Fixed typo. Revision ChangesPath 1.44 +1 -1 xml-xalan/c/src/XalanTransformer/XalanTransformer.cpp Index: XalanTransformer.cpp

[GUMP] Xalan2 Smoketest Failure

akarta/xml-xalan/test/java/build/xalan-smoketest-20020327.tar [tar] Entry: xml-xalan/test/smoketest/api/SAXTransformerFactoryAPITest/trax/sax/SAXTransformerFactoryAPITest_1.out longer than 100 characters. [tar] Resulting tar file can only be processed successfully by GNU compatib

Transforming memory grows (Xalan-C)

I have a complex stylesheet using a small input (2MB) to generate a bigger (but not so big) output (20MB). Applying this Stylesheet allocates 260MB of memory. I found most of the memory can be saved, if I use a special form of "xsl:with-param". Take *big* XML-Document an apply with testXSLT th

Re: How can I serialize my XML doc with an opening and closing tag

>How can I explicitly serialize my node as ? I don't think our serializer currently allows you to control that. XML considers and to be completely equivalent, so arguably you shouldn't _need_ to control it... It'd be possible to modify Xalan to add a non-standard feature which allowed tellin

How can I serialize my XML doc with an opening and closing tag

I would like to serialize my Document with Xalan but the problem is that if the element is empty, it serializes it as .   How can I explicitly serialize my node as ?    Thanks. Vincent  

Re: Making Xalan XSLTC work with Cocoon

It sounds like you guys have the ball right now. Let us know if there's something we can do, beyond the usual. -scott

Re: StreamSource Question

>I am trying to build a Transformer from a String, so I am creating a StringReader as a >StreamSource. I know that the String contains a valid XSLT document. >Is there any reason this should not work? Not that I can think of. More details about why you think it isn't working might help us advise

Re: Making Xalan XSLTC work with Cocoon

On Wednesday 27 March 2002 04:42 am, Stefano Mazzocchi wrote: > I fully believe in the power of communities and I strongly believe that > no single person, no matter how smart and brilliant, can match the power > of the distributed IQ of a sane and focused open development community. How about Mi

Making Xalan XSLTC work with Cocoon

One day I decided to see what could be done to address the fact that server-side XSLT transformations might become a serious performance bottleneck for massive use of cocoon. So I went ahead and did some tests on my machine, these were not extensive enough for a published paper, but they were ok

cvs commit: xml-xalan/test test.properties

sboag 02/03/27 04:48:32 Modified:test test.properties Log: Excluded javaBugzilla3722.xsl;libraryNodeset03.xsl;libraryNodeset01.xsl;javaRedir1.xsl;javaRedir2.xsl to make the smoketest pass. Need to investigate. Revision ChangesPath 1.49 +2 -0 xml-xalan

Re: SQL Extension

The NPE may be what he is experiencing. Gary helped him through one layer of his problem, I think. See http://marc.theaimsgroup.com/?t=10171605323&r=1&w=2. The thread is on xalan-j-users, which is perhaps why you missed it? -scott