Tim Bachta wrote:
I got the xml by using the cocoon-view=debug1.

Use a pipeline which places an XML serializer directly after the XSP generator, download the XML to a file from the browser, and have a look at the content of message-text. Does it look the same as what you posted, or does it more look like <message-text>null&lt;P toUpdate="1">&lt;STRO...

And I do have apply
templates for P and STRONG and A

This is not what I asked.


Hey c'mon, I can't play this "guess what I know" indefinitely.
Trim down the XSP so that it generates just one line of the
text inquestion, and the XSLT so that it transforms it into
just one fo:block, then post both, the XSLT without the
unimportant layout-master-set and static content stuff.

J.Pietschmann



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to