> Date: Tue, 6 Jan 2015 18:40:07 +0100
> From: oliver.he...@oliver-heger.de
> To: user@commons.apache.org
> Subject: Re: [configuration] Adding CData to xml property
> 
> 
> 
> On 06.01.2015 17:55, jeevi tesh wrote:
> > Hi,
> >
> > Need to add CDATA into XML Property element, but special character are
> > getting added. Here is my code. Please give your thoughts on the same.
> >
> > Here is the code.
> >
> > String cDataTagStart="\\<![CDATA[";
> >
> > String cDataTagEnd="]]\\>";
> >
> > credentialsURL =cDataTagStart+credentialsURL+cDataTagEnd;
> >
> > xmlContentOfMetaData = CredentialProvider.*getInstance*();
> >
> > xmlContentOfMetaData.addProperty("Resource(-1).ResourceName", resourceName);
> >
> > xmlContentOfMetaData.addProperty("Resource.ResourceURL", credentialsURL);
> >
> >
> >
> > But Special characters are getting added
> >
> > ResourceName>TESTRESOURCENAME</ResourceName>
> >
> > <ResourceURL>\&lt;![CDATA[TESTCredentialsURLS2]]\&gt;</ResourceURL>
> >
> 
> XMLConfiguration ensures that for newly added or updated properties 
> valid XML is generated. Therefore, special characters are encoded 
> automatically. This frees applications from the burden to do the 
> encoding manually. However, there is less control of the XML generated.
> 
> Currently, XMLConfiguration does not supported the generation of CDATA 
> sections. You may want to add a feature request in our bug tracking 
> system [1].

MG>In the meanwhile why not use StringBuffer to concatenate the Unicode 
equivalent for your CDATA
MG>example: this prints the Unicode equivalent of the divisor character '÷'
MG>System.out.println("\\u" + Integer.toHexString('÷'|0x10000).substring(1) )> 

> Oliver
> 
> [1] 
> http://commons.apache.org/proper/commons-configuration/issue-tracking.html
> 
> >
> > Thanks
> >
> > jeevitesh
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
> 
                                          

Reply via email to