Luca Morandini wrote:
Answer to your question: Yes, anomaly; No, it is not supposed to work this way. My take is that any change in transformer configuration should not affect output -- in the end, it's supposed to work in accordance with the spec.Folks,I've sent the following message a couple days ago and no answer came. I'd like only to know whether this is an anomaly to put into BugZilla, or it is the intended behaviour: any good soul listening ?
So yes, sounds like bug, but I have no idea how to fix it. Hope xalanians know better.
Vadim
Best regards,
P.S.
By the way, I deem this mis-handling of the document() function serious
enough, since it breaks Cocoon's XSLT support
---------------------------------------------
Luca Morandini
GIS Consultant
[EMAIL PROTECTED]
http://utenti.tripod.it/lmorandini/index.html
---------------------------------------------
-----Messaggio originale-----
Da: Luca Morandini [mailto:spectrum.morandini@;ipzs.it]
Inviato: mercoledì 23 ottobre 2002 14.09
A: Cocoon-dev
Oggetto: Is this as anomaly ?
Folks,
When the "incremental-processing" attribute of the XSLT-processor
is set to
"true", the "document()" XSLT function returns a string and NOT a node-set
(as
it is supposed to do).
Hence, if you want something like:
<xsl:copy-of select="document('test.xml')"/>
to work properly, youd should modify cocoon.xconf, setting
"inremental-processing" to "false", like in:
<xslt-processor
class="org.apache.cocoon.components.xslt.XSLTProcessorImpl"
logger="core.xslt-processor">
<parameter name="use-store" value="true"/>
<parameter name="incremental-processing" value="false"/>
</xslt-processor>
Is this as an anomaly or it supposed to behave this way ?
Best regards,
P.S.
BTW, in Cocoon 2.0.2 the default was "false", while in the 2.0.3 it is
"true", therefore, I hade an hard time to figure this out :(
---------------------------------------------
Luca Morandini
GIS Consultant
[EMAIL PROTECTED]
http://utenti.tripod.it/lmorandini/index.html
---------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
