Both SAAJ and servicemix-http components only handle the SOAP protocol. It is the responsibility of the consumer to send an xml request which is compliant with the WSDL of the consumed service. The consumer does not need to know about SOAP, but it needs to know the abstract WSDL description of the service so that it can build a valid request.
On 12/27/06, Maxim Y. Tebenev <[EMAIL PROTECTED]> wrote:
Guillaume, thank you for your reply! Ok, that works fine for consumer -> provider transformation. I've encountered with another issue when transforming provider -> provider transformation. The route is following: consumer -> XSL transform -> provider1 -> XSL transform -> provider2 The problem relies somewhere between provider1 and provider2. When SMX receives response from provider1 it puts all HTTP headers from response and sends them to provider2. In result I have time-out error on client and HTTP 500 error on provider2. Is there any way to remove those headers from the first response? Another intriguing question is the following: having provider2 WSDL ESB can construct valid SOAP request without XSL (that's my guess of course). My task is just get parameters from provider1 response and put them to provider2 request without known SOAP request details. Is that possible? I've heard the magic word SAAJ but that component deprecated in favor of HTTP. What do you say? Best regards, Maxim Tebenev. -- View this message in context: http://www.nabble.com/consumer-to-provider-SOAP-transformation-tf2883435s12049.html#a8061851 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet
