Hello! I'm attempting to evaluate ServiceMix for a specific application. I've downloaded 4.3.0 and have it running stand-alone. It's running in on a Windows XP SP3 environment using Sun's (Oracle's) 1.6 JVM (build 1.6.0_06-b02). My customizations so far have been isolated to a single xbean.xml file copied to the deploy folder. What I'm trying to do is to have ServiceMix periodically call a remote REST web-service and then parse and transform the response to generate calls to a different web-service sending a SOAP message (basically, a bridge-type application). I've managed to get much of the functionality tested, but have run into an interesting problem. It appears that the when reading the response from the first web-service (REST) the XML message response content is getting garbled, specifically entities having multiple instances are being removed.
In the attached http://servicemix.396122.n5.nabble.com/file/n3714422/sample_xbean.xml sample_xbean.xml file you will see a simplified version of the xbean.xml file being used. In the attached http://servicemix.396122.n5.nabble.com/file/n3714422/sample.xml sample.xml file you will see a (redacted) sample response being returned by the REST web-service. In the attached http://servicemix.396122.n5.nabble.com/file/n3714422/servicemix_log_snippet.txt servicemix_log_snippet.txt file is a redacted version of what is being recorded to the ServiceMix log file As you can see, not only is the second "purchase-order" element being removed, but the second "po-line" inside the first "purchase-order" element has also been removed. I've validated that the response REST message is being returned as expected when queries using a browser and that the response message itself is valid XML (used multiple tools, including on-line tools to validate the XML). Just in case, I wrapped the response message in a SOAP envelop, but that had no impact. The log had the exact same contents (i.e. the SOAP envelop elements were removed as were other elements in the message body). As you can imagine, the service will only work properly if the messages can be passed to subsequent endpoints unmolested. Is this a known issue and if so are there any workarounds? I realize I could code my own endpoint handler for the REST service, but I'd like to limit my customizations to XML and XSLT files for the time being as I'm still only evaluating the software. Thanks! -- View this message in context: http://servicemix.396122.n5.nabble.com/http-producer-XML-response-missing-elements-tp3714422p3714422.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
