This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Creating a cdata section using xsl
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: RE: [xsl] Creating a cdata section using xsl
- From: "Ben Robb" <b dot robb at cscape dot com>
- Date: Tue, 27 Feb 2001 15:31:58 -0000
- Reply-To: xsl-list at lists dot mulberrytech dot com
- thread-index: AcCgwUWpq/EilGyCQPKwNYPkp2IsPQADAb7g
- Thread-Topic: [xsl] Creating a cdata section using xsl
<snip>
I am creating one XML document
that is acting as a transport mechanism to other systems. The cdata
section
encapsulated in the display tag contains information that is only
understood
by the recipient objects. In your implementation the objects that
package
and send the data would be enormously complex because they would have to
understand the data structures of every object they send data to.
</snip>
Why would it have to understand the data if you didn't want it to? Just
use a copy, or a copy-of, or a <xsl:template match="*"> to do generic
stuff... that way your XSLT will just process anything it comes across.
BTW - if this is really what you are doing, I would have a serious look
at SOAP, which does exactly this, but is a standard. Why reinvent the
wheel?
Ben
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list