tentstitcher@gmail.com wrote:[color=blue]
> Thanks for reply. The source document and the target document are both
> SOAP messages. The <stringData> element is read out of the source's
> SOAP Body and has to be placed in the target's SOAP Body. The < and
> > have to be converted before being added to the target SOAP body so
> that the body now contains an new xml element.[/color]
as Richard said, you can try :
<xsl:value-of select="text()" disable-output-escaping="yes"/>
but the output will be broken if the tags are not well-balanced, which
is the case in your example
you should consider an alternative tool such as RefleX (
http://reflex.gforge.inria.fr/ ) that can fix invalid markup thanks to
an HTML parser ; the process would be :
<xcl:parse name="input" source="file:///path/to/input.xml"/>
<xcl:parse-html name="data" text-source="{ string( $input/stringData ) }"/>
<xcl:document name="result">
<stringData>
{ $data }
</stringData>
</xcl:document>
<xcl:transform source="{ $result }" output="file:///path/to/result"/>
there are also means to update the $input, by replacing the old content
of <stringData> with the new one, made of markup
[color=blue]
>
> I tried the suggestion, yet the SOAP output of the XSLT retains the
> < and > occurances.
>
> Thanks
>[/color]
--
Cordialement,
///
(. .)
--------ooO--(_)--Ooo--------
| Philippe Poulard |
-----------------------------
http://reflex.gforge.inria.fr/
Have the RefleX !
