Hi, I have problem with java-code generated from my wsdl (using the eclipse tool). The Soap messages (which the client sends, or the server understands) do not match the wsdl. The wsdl is using document/literal style and is WS-I compliant (but unfortunately I dont have it here).
First request shows the soap message which is produced with the classes generated with xfire. The second message is an example from SOAP-UI which shows the correct structure of the message as far as I understand (all the rest of the test tools create more or less similiar structure for the soap message as soap-ui). So whats the magic to get XFire to produce and understand correct soap messages? I havent found any concrete guide in the xfire site. I remember seeing some mentions of how to remove te <in0> structure but im not able to find them anymore. Wrong: <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:Body> <userInfo xmlns="http://tempuri.org";> <in0> <fileType xmlns="http://model.tempuri.org";></fileType> <fileSet xmlns="http://model.tempuri.org";></fileSet> </in0> </userInfo> </soap:Body> </soap:Envelope> Right: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:cor="http://tempuri.org/FileService"; xmlns:mod="http://model.tempuri.org/";> <soapenv:Header/> <soapenv:Body> <cor:userInfoRequestElement> <mod:fileSet>?</mod:fileSet> <mod:fileType>?</mod:fileType> </cor:userInfoRequestElement> </soapenv:Body> </soapenv:Envelope> Thanks for your help, Tero --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
