Hi, actually, I find both your wsdl and client code to be wrong, but I suppose your wsdl was simply corrupted when it was pasted into your mail.
In concrete, your our wsdl document is missing the namespace declarations for prefixes wsdl, soap, xs, and tns that are used in the rest of the document. So, I assume that you had the following declarations in your wsdl xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:xs="http://www.w3.org/2001/XMLSchema"; xmlns:tns="http://alerts.webservice.mbpportal.mbs.mycompany.com/"; Suppose your wsdl had the above declarations, we look at your code. Your code is wrong because you seem to be filling the structure with the plain string value instead of filling the complex structure. You can refer to my example that I posted a few days ago on this thread. You can just replace the operation qname that I used iin my example with the following one that matches your wsdl's operation definition. QName opName = new QName("http://alerts.webservice.mbpportal.mbs.mycompany.com/";, "getAlertData"); Then, you can get the soap message formartted as: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> <soap:Body> <ns2:getAlertDataRequest xmlns:ns2="http://alerts.webservice.mbpportal.mbs.mycompany.com/";> <user>Anne</user> </ns2:getAlertDataRequest> </soap:Body> </soap:Envelope> Regards, aki 2011/5/2 srinivas thallapalli <[email protected]>: > Hi Aki/Daniel, > > Could you please let me know, if there anything wrong with WSDL and client > code?. > > Thanks > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Problem-with-CXF-tp4341066p4364053.html > Sent from the cxf-user mailing list archive at Nabble.com. >
