Sylvain Wallez wrote:
IIRC (but don't ask me why), the XSP engine wraps every text node from
the XSP file into xsp:text elements.
In the original implementation text nodes were preprocessed and escaped
as string constants in accordance to the rules of the target programming
language. This took
Ricardo Rocha wrote:
Sylvain Wallez wrote:
IIRC (but don't ask me why), the XSP engine wraps every text node
from the XSP file into xsp:text elements.
In the original implementation text nodes were preprocessed and
escaped as string constants in accordance to the rules of the target
Sylvain Wallez wrote:
Ricardo Rocha wrote:
snip/
So xsp:text is probably a venerable fossil today. That said, if it
ain't broken...
Ah yes, I remember that, now. Gosh, the ancient times of Cocoon 1.x...
Thanks for refreshing our memory, Ricardo.
In fact, I was refering to the first Cocoon *2*
Silly mail client!
Hi all,
I building an XSP Java logicsheet, and use the following constructs:
xsl:template match=* mode=ctrl-mode
xsp:logic
xsl:apply-templates select=@* mode=ctrl-mode/
this.contentHandler.startElement(
Geissel, Adrian wrote:
Silly mail client!
Hi all,
I building an XSP Java logicsheet, and use the following constructs:
xsl:template match=* mode=ctrl-mode
xsp:logic
xsl:apply-templates select=@* mode=ctrl-mode/
this.contentHandler.startElement(
: Strange XSLT behaviour in logicsheet
when matching
text() nodes (resent)
Geissel, Adrian wrote:
Silly mail client!
Hi all,
I building an XSP Java logicsheet, and use the following constructs:
xsl:template match=* mode=ctrl-mode
xsp:logic
xsl:apply
