I assume that <test><![CDATA[this <is> text]]></test> and
<test>this <is> text</test> should be received
off the wire in a String as "this <is> text".
The problem is that when "this <is> text" is serialized, it
is always serialized as <test>this <is> text</test>.
So there needs to be a way to mark this particular string
so that it should be serialized as test><![CDATA[this <is> text]]></test>
One way is to have an option in the runtime to use the CDATA encoding
style....but this is an all or nothing approach.
Another way is to support <!CDATA[...]]> sections in the String.
This would force the user to change their String from "this <is> text" to
"<![CDATA[this <is> text]]>" which seems to be a reasonable work-around to
prevent encoding.
Comments ?
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
James M
Snell/Fresno/IBM@ To: [EMAIL PROTECTED]
IBMUS cc: Sam Ruby/Raleigh/IBM@IBMUS,
Doug Davis/Raleigh/IBM@IBMUS
Subject: Axis CDATA Problem
02/28/2002 12:19
PM
Please respond to
axis-dev
Axis appears to have a problem with CDATA sections. When a message is
received by Axis that contains a CDATA section, it does not appear to
properly reserialize it as a CDATA section. Rather, it is serialized as a
regular Text Node with escape characters.
In other words <test><![CDATA[this <is> text]]></test> comes out
<test>this <is> text</test>.
This is a significant problem if you're working with digital signatures or
your code is expecting a CDATA section.
- James M Snell/Fresno/IBM
Web services architecture and strategy
Internet Emerging Technologies, IBM
544.9035 TIE line
559.587.1233 Office
919.486.0077 Voice Mail
[EMAIL PROTECTED]
Programming Web Services With SOAP, O'reilly & Associates, ISBN
0596000952
==
Have I not commanded you? Be strong and courageous. Do not be terrified,
do not be discouraged, for the Lord your God will be with you wherever you
go.
- Joshua 1:9