Sylvain Wallez wrote:
Ricardo Rocha wrote:
So 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* XSP implementa
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 elements.
In the original implementation text nodes were preprocessed and
escaped as string constants in accordance to the rules of the target
programming lang
Sylvain Wallez wrote:
IIRC (but don't ask me why), the XSP engine wraps every text node from
the XSP file into 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 place prior
ect: Re: C2.0.4: Strange XSLT behaviour in logicsheet
> when matching
> text() nodes (resent)
>
>
> Geissel, Adrian wrote:
>
> >Silly mail client!
> >
> >
> >>Hi all,
> >>
&g
Geissel, Adrian wrote:
Silly mail client!
Hi all,
I building an XSP Java logicsheet, and use the following constructs:
this.contentHandler.startElement(
"",
"",
"",
xspAttr);
Silly mail client!
> Hi all,
>
> I building an XSP Java logicsheet, and use the following constructs:
>
>
>
>
> this.contentHandler.startElement(
> "",
> "",
> "",
> xsp
Hi all,
I building an XSP Java logicsheet, and use the following constructs:
this.contentHandler.startElement(
"",
"",
"",
xspAttr);
xspAttr.clear();
