This error is thrown when XFire can not find an xml element (I think it is the main element in the soap body). You should try to put all log levels to DEBUG and you should see the content of the JBI exchanges.
Cheers, Guillaume Nodet On 4/27/06, cheff <[EMAIL PROTECTED]> wrote: > > Hi > > I have troubles :-( > O.K. I have the XFire binder component running up. That's fine. > I'm not sure now if I want to call the service from browser should I expose > it through HttpBinder as shown in the soap-binding example? What is the > right way to do this acutlly? > I've tried through the http binder but I have such un error: > <?xml version="1.0" encoding="UTF-8" ?> > - <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> > - <soap:Fault> > <faultcode>soap:Client</faultcode> > <faultstring>There must be a method name element.</faultstring> > </soap:Fault> > </soap:Body> > </soap:Envelope> > > 10x > -- > View this message in context: > http://www.nabble.com/Using-lightweight-XFire-binding-t1511614.html#a4116695 > Sent from the ServiceMix - User forum at Nabble.com. > >
