I am using the most recent version of Xfire and I am running into an issue where I have a simple string XmlBean property that I set XML in and when XFire (actually I found that the code doing this is from the Woodstax BufferingXmlWriter class - method starting at line 488) is creating the body for the SoapEnvelope that is being sent in the web service request, it is converting (escaping) all < characters of my xml to <.
Here is the XML that I set on the ImportData object xml attribute (input object to the web service operation I am calling): Fields from class com.fusionalliance.fusionsoft.downloads.ws.ImportData: xml: <dixon><child>ddd</child></dixon> validateXmlAgainstSchema: false continueProcessingIfErrors: true And Xfire is producing this SoapEnvelope - notice all the < strings that I would expect to be a < symbol (or at least I'd expect the > symbol to be converted to :gt;) : 2008-04-25 14:55:41,131 DEBUG [httpclient.wire.content] (AWT-EventQueue-0:) >> "<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soap:Header><type xmlns="http://www.fusionalliance.com/fusionsoft/downloads/ws">StandardIm port</type></soap:Header><soap:Body xmlns:ns1="http://www.fusionalliance.com/fusionsoft/downloads/ws"><ns1:i mportData><ns1:xml><dixon><child>ddd</child></dixon></ns1:xm l><ns1:validateXmlAgainstSchema>false</ns1:validateXmlAgainstSchema><ns1 :continueProcessingIfErrors>true</ns1:continueProcessingIfErrors></ns1:i mportData><ns1:type>StandardImport</ns1:type></soap:Body></soap:Envelope >" Has anyone else run into this? Do I have something configured incorrectly. Other than this issue, xfire has worked great for us. Thanks, Bryan
