The exception at the client:
2009-02-04 10:42:46,007 [main|INFO]
=======================================================
org.apache.axis2.AxisFault: Transport level information does not match with
SOAP Message namespace URI
    at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
    at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:90)
    at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:353)
    at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
    at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
    at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
    at
com.gallup.soap.wsdl.roadbed.main12.ConsumerService12Stub.doWork(ConsumerService12Stub.java:186)
    at
com.gallup.soap.client.roadbed.main.Client.doWorkSmx12(Client.java:98)
    at com.gallup.soap.client.roadbed.main.Client.main(Client.java:397)
Caused by: org.apache.axiom.soap.SOAPProcessingException: Transport level
information does not match with SOAP Message namespace URI
    at
org.apache.axis2.builder.BuilderUtil.validateSOAPVersion(BuilderUtil.java:761)
    at
org.apache.axis2.builder.SOAPBuilder.processDocument(SOAPBuilder.java:55)
    at
org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:164)
    at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:112)
    at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:88)
    ... 7 more

On Wed, Feb 4, 2009 at 10:24 AM, Asen <[email protected]> wrote:

> I am trying to connect Axis2 version 1.4.1 deployed web service and
> ServiceMix 3.3 through consumer/provider endpoints.
> When using the old endpoints the SA got deployed, but when tried to execute
> the pipeline the Axis2 threw up due to the internal check between the
> request Content-Type and the namespace of the SOAP envelope as per
> http://wso2.org/library/559
>
> POST /jbi/ConsumerService12/ HTTP/1.1
> Content-Type: *application/soap+xml*; charset=UTF-8; action="urn:doWork"
> User-Agent: Axis2
> Host: 127.0.0.1:8081
> Transfer-Encoding: chunked
>
> 204
> <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="
> http://www.w3.org/2003/05/soap-envelope";><soapenv:Header xmlns:wsa="
> http://www.w3.org/2005/08/addressing";><wsa:To>
> http://asen.gallup.com:8081/js/jbi/ConsumerService12/</wsa:To><wsa:MessageID>urn:uuid:447FDAA17B8E22B6381233762375181</wsa:MessageID><wsa:Action>urn:doWork</wsa:Action></soapenv:Header><soapenv:Body><ns1:doWork
> xmlns:ns1="http://webservices.gallup.com";><ns1:message>Asen</ns1:message></ns1:doWork></soapenv:Body></soapenv:Envelope>
>
> 0
>
> HTTP/1.1 500 Internal Server Error
> Server: Apache-Coyote/1.1
> Content-Type: *text/xml*;charset=UTF-8
> Transfer-Encoding: chunked
> Date: Wed, 04 Feb 2009 15:46:15 GMT
> Connection: close
>
> 1af
> <?xml version='1.0' encoding='UTF-8'?><*soapenv*:Envelope *xmlns:soapenv*=
> *"http://www.w3.org/2003/05/soap-envelope"*><soapenv:Body><soapenv:Fault><soapenv:Code><soapenv:Value>soapenv:Receiver</soapenv:Value></soapenv:Code><soapenv:Reason><soapenv:Text
> xml:lang="en">java.lang.IllegalArgumentException: Bad syntax: expected
> [part0][sep][part1][sep][part2]</soapenv:Text></soapenv:Reason></soapenv:Fault></soapenv:Body></soapenv:Envelope>
>
> 0
>
>
> When using the new http end points <http:soap-consumer ... >
> <http:soap-provider ... >, the SA failed to load due to WSDL is not WS-I BP,
> caused by a SOAP 1.2 port binding.
>
> Is there a way to overcome this with some setting in servicemix 3.3 with
> the current servicemix-http component, or not posible at all ?
> Axis2 as of now will always expect the Content-Type of the request to match
> the soap envelope namaspace, which will
> make it incompatible for use of SOAP 1.2 with ServiceMix 3.3
>
> java.lang.Exception: <?xml version="1.0" encoding="UTF-8"?><jbi-task
> xmlns="http://java.sun.com/xml/ns/jbi/management-message"; version="1.0">
> <jbi-task-result>
> <frmwk-task-result>
> <frmwk-task-result-details>
> <task-result-details>
> <task-id>deploy</task-id>
> <task-result>FAILED</task-result>
> <message-type>ERROR</message-type>
> </task-result-details>
> </frmwk-task-result-details>
> </frmwk-task-result>
> <component-task-result>
> <component-name>servicemix-http</component-name>
> <component-task-result-details>
> <task-result-details>
> <task-id>deploy</task-id>
> <task-result>FAILED</task-result>
> <message-type>ERROR</message-type>
> <task-status-msg>
> <msg-loc-info>
> <loc-token/>
> <loc-message>Unable to parse result string</loc-message>
> </msg-loc-info>
> </task-status-msg>
> <exception-info>
> <nesting-level>1</nesting-level>
> <loc-token/>
> <loc-message>WSDL is not WS-I BP compliant: [binding "{
> http://webservices.gallup.com}WorkWebServiceHttpSoap12EndpointBinding"; :
> Basic Profile Violation #R2401: A wsdl:binding element in a DESCRIPTION MUST
> use WSDL SOAP Binding as defined in WSDL 1.1 Section 3.]</loc-message>
> <stack-trace><![CDATA[javax.jbi.management.DeploymentException: WSDL is not
> WS-I BP compliant: [binding 
> "{http://webservices.gallup.com}WorkWebServiceHttpSoap12EndpointBinding";
> : Basic Profile Violation #R2401: A wsdl:binding element in a DESCRIPTION
> MUST use WSDL SOAP Binding as defined in WSDL 1.1 Section 3.]
>     at
> org.apache.servicemix.http.endpoints.HttpSoapConsumerEndpoint.validateWsdl1(HttpSoapConsumerEndpoint.java:183)
>     at
> org.apache.servicemix.http.endpoints.HttpSoapConsumerEndpoint.validate(HttpSoapConsumerEndpoint.java:149)
>     at
> org.apache.servicemix.common.AbstractDeployer.validate(AbstractDeployer.java:58)
>     at
> org.apache.servicemix.common.xbean.BaseXBeanDeployer.validate(BaseXBeanDeployer.java:55)
>     at
> org.apache.servicemix.common.xbean.AbstractXBeanDeployer.deploy(AbstractXBeanDeployer.java:96)
>     at
> org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:88)
>     at
> org.apache.servicemix.common.BaseServiceUnitManager.deploy(BaseServiceUnitManager.java:69)
>     at
> org.apache.servicemix.jbi.framework.DeploymentService.deployServiceAssembly(DeploymentService.java:508)
>     at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateServiceAssembly(AutoDeploymentService.java:353)
>     at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:256)
>     at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:667)
>     at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(AutoDeploymentService.java:62)
>     at
> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:631)
>     at java.util.TimerThread.mainLoop(Timer.java:512)
>     at java.util.TimerThread.run(Timer.java:462)
> ]]></stack-trace>
> </exception-info>
> </task-result-details>
> </component-task-result-details>
> </component-task-result>
> </jbi-task-result>
> </jbi-task>
>
>     at
> org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:125)
>     at
> org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:111)
>     at
> org.apache.servicemix.jbi.framework.DeploymentService.deployServiceAssembly(DeploymentService.java:543)
>     at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateServiceAssembly(AutoDeploymentService.java:353)
>     at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:256)
>     at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:667)
>     at
> org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(AutoDeploymentService.java:62)
>     at
> org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:631)
>     at java.util.TimerThread.mainLoop(Timer.java:512)
>     at java.util.TimerThread.run(Timer.java:462)
>

Reply via email to