Folks,
the anomaly I've found (document XSLT function returning a string instead of
a node-set) is linked to the Xalan version AND the incremental-processing
parameter.
It could be summarized as follows:
1) Xalan 2.2.0.D14 and incremental-processing set to true: Error
2) Xalan 2.2.0.D14
Luca Morandini wrote:
Vadim,
thanks, one can always trust you :)
Just two things:
1) I'll submit the bug to BugZilla
2) You (developers) set incremental-processing to false by default in
2.1 and 2.0.4
Let me know bug # and I will change the default in 2.0.4.
Vadim
Best regards,
Luca
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 ?
Best regards,
P.S.
By the way, I deem this mis-handling of the document() function
Luca Morandini wrote:
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 ?
Answer to your question: Yes, anomaly; No, it is not supposed
[mailto:vadim.gritsenko;verizon.net]
Inviato: venerdì 25 ottobre 2002 15.27
A: [EMAIL PROTECTED]
Oggetto: Re: R: Is this as anomaly ?
Luca Morandini wrote:
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
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