Ah, nevermind, i found my problem: the http provider endpoint representing the external service was configured with an incorrect soap version
ender wrote: > > Well, I'm building a proxy web service for an existing, rpc/encoded web > service. While the http consumer endpoint accepts the request just fine, > the response it returns isn’t rpc/encoded style, so my JAX-RPC client > doesn’t understand it. > > > gnodet wrote: >> >> RPC-encoded is not really supported. >> However the http BC does not really care of the soap body content >> itself, so if you send the right body content, it should work. >> What kind of problems do you have ? >> >> On 12/20/06, ender <[EMAIL PROTECTED]> wrote: >>> >>> Hello, >>> >>> Is there a way to have an http consumer endpoint generate a RPC-encoded >>> wsdl, instead of the default document-literal one? >>> >>> Thanks, >>> Stein >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Http-Endpoint%3A-rpc-encoded-generation-tf2859019s12049.html#a7987817 >>> Sent from the ServiceMix - User mailing list archive at Nabble.com. >>> >>> >> >> >> -- >> Cheers, >> Guillaume Nodet >> >> > > -- View this message in context: http://www.nabble.com/Http-Endpoint%3A-rpc-encoded-generation-tf2859019s12049.html#a7991963 Sent from the ServiceMix - User mailing list archive at Nabble.com.
