Issue 52: escapeSpecialchars
Status:  Fixed
Owner: ----
Closed:  Apr 2012
Reported by vijays...@gmail.com, Sep 9, 2011
Documentation does not explain how to escape Special Characters with a CDATA tag. 


Sep 19, 2011
#2 achim.r...@gmail.com
Hi, I have a problem with the special chars too. I need to change "\n" to "
" and set 

FlexXBEngine.instance.configuration.escapeSpecialChars = false;

I build my own StringConverter where i replaced the chars. But in the end I get "
" instead of "
"

I would guess it's the com.googlecode.flexxb.xml.serializer.XmlElementSerializer.

I didn't see that you don't escape the special chars. Just in case of an exception (???).

Best reagards
Achim
Sep 19, 2011
Project Member #3 alex.id....@gmail.com
Oops, you're right. By default, you do not need to set that flag to true. When there is a problem building the xml element(special chars present) the exception is cought and the element is escaped by setting up a CDATA tag. If you set escape SpecialChars to true then it will phisically escape every special char it finds. 

Achim, this woul seem to be an issue, either with FlexXB of Flex's XML builder. Can you provide me with a small sample?

Thanks
Sep 19, 2011
#4 achim.r...@gmail.com
Here you go, 
see the attached sample
FlexXBSample.zip
65.6 KB   Download
Sep 30, 2011
Project Member #5 alex.id....@gmail.com
(No comment was entered for this change.)
Labels: Milestone-2.3.1
Apr 14, 2012
Project Member #6 alex.id....@gmail.com
Seems there is a change in teh way children are appended. Now they escape strings by default so the try catch is pretty much useless. I've added a new option in XmlElement, wrapCDATA, which will automatically wrap the values in a CDATA tag and preserve the value's existing structure.
Status: Started
Apr 14, 2012
Project Member #7 alex.id....@gmail.com
(No comment was entered for this change.)
Status: Fixed