You can't do this easily. CXF is based on XML, and, in XML, there is officially _no difference at all_ between those characters escaped with ampersands and escaped with cdata. Any program that behaves differently is, from an XML standards point of view, broken.
If you need to deal with such a program, you need to learn how to make an interceptor to do what you want. It might be possible to configure Woodstox to do what you want and then to impose that configuration into your stack. --benson On Wed, Nov 24, 2010 at 10:39 AM, hsemar <[email protected]> wrote: > > How do I handle the special characters in web service request > > I have a web service method and here is the sample request > > <request> > <id>1<id> > <desc>this is desc of > <itemid>1</itemid><itemname>ipod</itemname></desc> > <category>2</category> > </request> > > desc element type is string in my schema file. > > When I create client stub and test this, the < and > characters inside > <desc> element are converted into ;lt and ;gt respectively and everything > works fine. > > But when I test this same service using SoapUI, the charatcters are not > being converted and I get unmarsshalling error which is fair. > > So, now how do I make sure the data inside the <desc> element is not > processed ? Do I need to write a handler and acheive this in the server > side? > > Is there anyway that we can say this element should be wrapped with CDATA ? > I know it is not possible in the XSD schema. I'm mostly looking for a server > side (web service level not at the client level) solution > > Also, I would like to remove some set of special characters from the soap > request before the request is used inside the web service method..any idea? > > I would like to get your valuable suggestions on this. > -- > View this message in context: > http://cxf.547215.n5.nabble.com/How-to-enforce-the-clients-to-use-CDATA-for-specific-elements-tp3278597p3278597.html > Sent from the cxf-user mailing list archive at Nabble.com. >
