發文作者:wekon | 五月 9, 2010

invoke fail when executing ws bpel engine

[environment]

activebpel engine 2.1.1 + tomcat 5.5.27 + win 7

[steps]

1. deploy process and web service
2. send request to wsbpel engine

[error message]

first of all, no error message appears, but invoke fail
after:

add: e.printStackTrace(); in org.activebpel.rt.axis.bpel.AeInvokeHandler(156), that is,
before: setFaultOnResponse(portTypeNamespace, operation, e, response);

the following error appears

AxisFault
faultCode: {http://xml.apache.org/axis/}Client
faultSubcode:
faultString: No such operation ‘parameters’
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:wekon

No such operation ‘parameters’
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:221)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:128)
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
at org.activebpel.rt.axis.bpel.handlers.AeXPathReceiveHandler.invoke(AeXPathReceiveHandler.java:60)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:190)
at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
at org.apache.axis.client.Call.invoke(Call.java:2748)
at org.apache.axis.client.Call.invoke(Call.java:1784)
at org.activebpel.rt.axis.bpel.invokers.AeDocumentStyleInvoker.invokeDocumentCall(AeDocumentStyleInvoker.java:124)
at org.activebpel.rt.axis.bpel.invokers.AeDocumentStyleInvoker.invoke(AeDocumentStyleInvoker.java:57)
at org.activebpel.rt.axis.bpel.AeInvokeHandler.handleInvoke(AeInvokeHandler.java:148)
at org.activebpel.rt.bpel.server.engine.invoke.AeInvoker.handleInvoke(AeInvoker.java:192)
at org.activebpel.rt.bpel.server.engine.AeInMemoryQueueManager$1.run(AeInMemoryQueueManager.java:117)
at org.activebpel.work.AeDelegatingWork.run(AeDelegatingWork.java:73)
at org.activebpel.work.AeProcessWorkManager$AeProcessWork.run(AeProcessWorkManager.java:265)
at org.activebpel.work.AeDelegatingWork.run(AeDelegatingWork.java:73)
at org.activebpel.work.AeExceptionReportingWork.run(AeExceptionReportingWork.java:51)
at org.activebpel.work.AeWorkerThread.run(AeWorkerThread.java:154)

[analysis]

invoke style is recognized as “document", not “rpc", so that the operation is incorrectly recognized

[solution]

modify the style attribute of <wsdlsoap:binding> from “document", which is automatically assigned by eclipse, to “rpc"


Responses

  1. hello Nice topic shutterfly coupon http://www.prweb.com/releases/Shutterfly/Coupons/prweb10850147.htm


發表迴響

在下方填入你的資料或按右方圖示以社群網站登入:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / 變更 )

Twitter picture

You are commenting using your Twitter account. Log Out / 變更 )

Facebook照片

You are commenting using your Facebook account. Log Out / 變更 )

Google+ photo

You are commenting using your Google+ account. Log Out / 變更 )

連結到 %s

分類

%d 位部落客按了讚: