This is more than likely to do with your schema definition - how you are defining FreightEstimationRequest. Point your wsdl at a tool like soapui and see what sort of xml it generates.
On 2/20/07, denis.wang <[EMAIL PROTECTED]> wrote:
I have a wsdl file and use wsgen to create xml beans first and then the client. However, the generated sample soap request looks like: <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> <getFrightAndHandlingCharges xmlns="http://mheducation.com/FreightEstimation";> <FreightEstimationRequest xmlns="http://mheducation.com/FreightEstimation/FreightEstimationRequest";> <FreightEstimationRequest> <AccountNumber xmlns="">94031</AccountNumber> Note that there is a <FreightEstimationRequest>element nested within an existing <FreightEstimationRequest>element. What's wrong? I just began to use xFire and got so frustrated that, my first try with jaxb has some weird problem and no response from this forum for a long time. The second try with xmlBeans binding still not working. Is xFire so buggy? I will try Axis if no luck anyway. Thanks. Denis -- View this message in context: http://www.nabble.com/is-xFire-so-buggy--Frustrated%3A-client-stub-error-using-xFire-%2B-XmlBeans-binding-tf3261757.html#a9065626 Sent from the XFire - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
