In my opinion, it's not the problem of smx, but the position of external web
service. When you send the invoke message to external WS, it can't be find
or error occurred; so application servera send the message back to smx which
smx can't understand and process.
engg_nawaz wrote:
>
> I am having the same scenario and same problem. Did u manage to solve it?
>
>
>
> baryzhongzsd wrote:
>>
>> Hello everybody,
>>
>> the scenario of my work is: Client-> HTTP Consumer endpoint->ODE
>> BPEL->HTTP Provider endpoint->external webservice.
>>
>> I have deployed the SA, the external WS successfully,
>> when I send the request to BPEL, the ODE didn't add enough namespace to
>> xml so that it cause the error as followed:
>>
>> ERROR - HttpComponent - Error processing exchange InOut[
>> id: ID:59.64.158.73-11db382e2a3-2:1
>> status: Active
>> role: provider
>> service: {cn.edu.bupt.InformConference.provide}informContext
>> endpoint: informContextService
>> operation: {cn.edu.bupt.InformConference.provide}contextWS
>> in: <?xml version="1.0" encoding="UTF-8"?><contextWS
>> xmlns="http://meet.adam.com";>//Here Lacks the soap namespace
>> <personName>Adam</personName>
>> <subject>hello</subject>
>> <host>Adam</host>
>> <remark>never give up!!</remark>
>> <meetDate>2008-11-22T03:37:22.343Z</meetDate>
>> </contextWS>
>> ]
>> org.apache.servicemix.soap.SoapFault: Unrecognized element: html at
>> [1,1]. Expecting 'Envelope'.
>> at
>> org.apache.servicemix.soap.marshalers.SoapReader.readSoapUsingStax(SoapReader.java:167)
>> at
>> org.apache.servicemix.soap.marshalers.SoapReader.read(SoapReader.java:89)
>> at
>> org.apache.servicemix.soap.marshalers.SoapReader.read(SoapReader.java:76)
>> at
>> org.apache.servicemix.http.processors.ProviderProcessor.process(ProviderProcessor.java:164)
>> at
>> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
>> at
>> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
>> at
>> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
>> at
>> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:610)
>> at
>> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:170)
>> at
>> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:167)
>> at
>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>> at java.lang.Thread.run(Thread.java:595)
>>
>> I clearly know that the right way to invoke the external service, however
>> i have checked all my deploy.xml, xBean.xml, bpel and wsdl; it seems all
>> the same to the one which my partner successfully deployed (he can not
>> say it either) . Hope someone can help me~
>>
>> http://www.nabble.com/file/p20575384/inform-bpel-sa-1.0-SNAPSHOT.jar
>> inform-bpel-sa-1.0-SNAPSHOT.jar
>>
>
>
--
View this message in context:
http://www.nabble.com/Problem-about-BPEL-invoke-external-web-service-tp20575384p23953678.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
