我有一个Web服务，它公开了几个以数组作为输入的方法。我已经根据mule-config.xml文件的要求为我的服务实现定义了一个流，并且可以从服务公开的WSDL创建我的WCF客户端。
如果我尝试调用其中一个接受数组作为客户端输入的方法，我会得到以下异常：
WARN 2011-10-06 13:38:02,139 [connector.http.mule.default.receiver.3] org.apache.cxf.phase.PhaseInterceptorChain: Interceptor for {http://api.data.ws.occ600.emsgt.com/}ConfigurationServiceService#{http://api.data.ws.occ600.emsgt.com/}create has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: Component that caused exception is: DefaultJavaComponent{configurationService.commponent.32217869}. Message payload is of type: MapExtent[]
at org.mule.module.cxf.MuleInvoker.invoke(MuleInvoker.java:85)
at org.mule.module.cxf.MuleJAXWSInvoker.invoke(MuleJAXWSInvoker.java:47)
at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:75)
at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106)
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:113)
at org.mule.module.cxf.CxfInboundMessageProcessor.sendToDestination(CxfInboundMessageProcessor.java:288)
at org.mule.module.cxf.CxfInboundMessageProcessor.process(CxfInboundMessageProcessor.java:129)
at org.mule.module.cxf.config.FlowConfiguringMessageProcessor.process(FlowConfiguringMessageProcessor.java:50)
at org.mule.processor.AbstractInterceptingMessageProcessor.processNext(AbstractInterceptingMessageProcessor.java:90)
at org.mule.processor.SecurityFilterMessageProcessor.process(SecurityFilterMessageProcessor.java:77)
at org.mule.processor.chain.DefaultMessageProcessorChain.doProcess(DefaultMessageProcessorChain.java:88)
at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:89)
at org.mule.processor.AbstractInterceptingMessageProcessor.processNext(AbstractInterceptingMessageProcessor.java:90)
at org.mule.processor.ExceptionHandlingMessageProcessor.process(ExceptionHandlingMessageProcessor.java:25)
at org.mule.processor.chain.DefaultMessageProcessorChain.doProcess(DefaultMessageProcessorChain.java:88)
at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:89)
at org.mule.processor.chain.InterceptingChainLifecycleWrapper.doProcess(InterceptingChainLifecycleWrapper.java:63)
at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:89)
at org.mule.processor.chain.InterceptingChainLifecycleWrapper.process(InterceptingChainLifecycleWrapper.java:94)
at org.mule.processor.chain.DefaultMessageProcessorChain.doProcess(DefaultMessageProcessorChain.java:88)
at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:89)
at org.mule.processor.chain.InterceptingChainLifecycleWrapper.doProcess(InterceptingChainLifecycleWrapper.java:63)
at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:89)
at org.mule.processor.chain.InterceptingChainLifecycleWrapper.process(InterceptingChainLifecycleWrapper.java:94)
at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:185)
at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:158)
at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:145)
at org.mule.transport.http.HttpMessageReceiver$HttpWorker.doRequest(HttpMessageReceiver.java:247)
at org.mule.transport.http.HttpMessageReceiver$HttpWorker.processRequest(HttpMessageReceiver.java:206)
at org.mule.transport.http.HttpMessageReceiver$HttpWorker.run(HttpMessageReceiver.java:164)
at org.mule.work.WorkerContext.run(WorkerContext.java:309)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Unknown Source)
Caused by: org.mule.component.ComponentException: Component that caused exception is: DefaultJavaComponent{configurationService.commponent.32217869}. Message payload is of type: MapExtent[]
at org.mule.component.DefaultComponentLifecycleAdapter.invoke(DefaultComponentLifecycleAdapter.java:359)
at org.mule.component.AbstractJavaComponent.invokeComponentInstance(AbstractJavaComponent.java:86)
at org.mule.component.AbstractJavaComponent.doInvoke(AbstractJavaComponent.java:77)
at org.mule.component.AbstractComponent.invokeInternal(AbstractComponent.java:120)
at org.mule.component.AbstractComponent.access$000(AbstractComponent.java:56)
at org.mule.component.AbstractComponent$1$1.process(AbstractComponent.java:234)
at org.mule.processor.chain.DefaultMessageProcessorChain.doProcess(DefaultMessageProcessorChain.java:88)
at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:89)
at org.mule.processor.chain.InterceptingChainLifecycleWrapper.doProcess(InterceptingChainLifecycleWrapper.java:63)
at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:89)
at org.mule.processor.chain.InterceptingChainLifecycleWrapper.process(InterceptingChainLifecycleWrapper.java:94)
at org.mule.component.AbstractComponent.process(AbstractComponent.java:154)
at org.mule.processor.AbstractInterceptingMessageProcessor.processNext(AbstractInterceptingMessageProcessor.java:90)
at org.mule.processor.AsyncInterceptingMessageProcessor.process(AsyncInterceptingMessageProcessor.java:97)
at org.mule.processor.chain.DefaultMessageProcessorChain.doProcess(DefaultMessageProcessorChain.java:88)
at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:89)
at org.mule.processor.AbstractInterceptingMessageProcessor.processNext(AbstractInterceptingMessageProcessor.java:90)
at org.mule.interceptor.AbstractEnvelopeInterceptor.process(AbstractEnvelopeInterceptor.java:55)
at org.mule.processor.AbstractInterceptingMessageProcessor.processNext(AbstractInterceptingMessageProcessor.java:90)
at org.mule.interceptor.AbstractEnvelopeInterceptor.process(AbstractEnvelopeInterceptor.java:55)
at org.mule.processor.AbstractInterceptingMessageProcessor.processNext(AbstractInterceptingMessageProcessor.java:90)
at org.mule.processor.AbstractFilteringMessageProcessor.process(AbstractFilteringMessageProcessor.java:41)
at org.mule.processor.chain.DefaultMessageProcessorChain.doProcess(DefaultMessageProcessorChain.java:88)
at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:89)
at org.mule.processor.chain.InterceptingChainLifecycleWrapper.doProcess(InterceptingChainLifecycleWrapper.java:63)
at org.mule.processor.chain.AbstractMessageProcessorChain.process(AbstractMessageProcessorChain.java:89)
at org.mule.processor.chain.InterceptingChainLifecycleWrapper.process(InterceptingChainLifecycleWrapper.java:94)
at org.mule.construct.AbstractFlowConstruct$1$1.process(AbstractFlowConstruct.java:107)
at org.mule.processor.AbstractInterceptingMessageProcessor.processNext(AbstractInterceptingMessageProcessor.java:90)
at org.mule.module.cxf.CxfInboundMessageProcessor.processNext(CxfInboundMessageProcessor.java:328)
at org.mule.module.cxf.MuleInvoker.invoke(MuleInvoker.java:80)
... 39 more
Caused by: org.mule.model.resolvers.EntryPointNotFoundException: Failed to find entry point for component, the following resolvers tried but failed: [
ArrayEntryPointResolver: Found too many possible methods on object "com.emsgt.occ600.ws.data.lib.ConfigurationServiceImpl$$EnhancerByCGLIB$$7277bad2" that accept parameters "{class [Lcom.emssatcom.occ600.dal.api.MapExtent;}", Methods matched are "[public final void com.emsgt.occ600.ws.data.lib.ConfigurationServiceImpl$$EnhancerByCGLIB$$7277bad2.delete(com.emsgt.data.api.EMSRecord[]) throws com.emssatcom.occ600.dal.api.DALException, public final com.emssatcom.occ600.dal.api.MapExtent[] com.emsgt.occ600.ws.data.lib.ConfigurationServiceImpl$$EnhancerByCGLIB$$7277bad2.create(com.emssatcom.occ600.dal.api.MapExtent[]) throws com.emssatcom.occ600.dal.api.DALException, public final void com.emsgt.occ600.ws.data.lib.ConfigurationServiceImpl$$EnhancerByCGLIB$$7277bad2.update(com.emssatcom.occ600.dal.api.MapExtent[]) throws com.emssatcom.occ600.dal.api.DALException, public final void com.emsgt.occ600.ws.data.lib.ConfigurationServiceImpl$$EnhancerByCGLIB$$7277bad2.createEx(com.emsgt.data.api.EMSRecord[]) throws com.emssatcom.occ600.dal.api.DALException, public final void com.emsgt.occ600.ws.data.lib.ConfigurationServiceImpl$$EnhancerByCGLIB$$7277bad2.updateOnly(com.emsgt.data.api.EMSRecord[]) throws com.emssatcom.occ600.dal.api.DALException, public final void com.emsgt.occ600.ws.data.lib.ConfigurationServiceImpl$$EnhancerByCGLIB$$7277bad2.updateOrInsert(com.emsgt.data.api.EMSRecord[]) throws com.emssatcom.occ600.dal.api.DALException]"
ReflectionEntryPointResolver: Could not find entry point on: "com.emsgt.occ600.ws.data.lib.ConfigurationServiceImpl$$EnhancerByCGLIB$$7277bad2" with arguments: "{class com.emssatcom.occ600.dal.api.MapExtent,class com.emssatcom.occ600.dal.api.MapExtent}"
]
at org.mule.model.resolvers.DefaultEntryPointResolverSet.invoke(DefaultEntryPointResolverSet.java:52)
at org.mule.component.DefaultComponentLifecycleAdapter.invoke(DefaultComponentLifecycleAdapter.java:350)
经过进一步调查，我找到了阵列入口点解析器。将此添加到我的mule-config中，如下所示
<component>
<entry-point-resolver-set>
<reflection-entry-point-resolver/>
<array-entry-point-resolver />
</entry-point-resolver-set>
<spring-object bean="myWebService"/>
</component>
仍然无济于事。有这个人的经验吗？
答案 0 :(得分：0)
我最终使用了数组入口点解析器，方法入口点解析器和API签名更改的组合来解决这个问题。这里的问题是Mule使用webservice调用的参数来确定使用哪个方法而不是方法名称，即使它的文档说明使用了一堆解析器，包括方法入口点解析器。
因此，如果你有一个接口公开两个不同命名的方法，两个都接受一个T类型的单个数组，那么就没有任何解析器组合可以确保调用正确的方法。不是我能说的。如果在method-entry-point-resolver集合中指定这两个方法，如下所示：
<method-entry-point-resolver>
<include-entry-point method="method1"/>
<include-entry-point method="method2"/>
</method-entry-point-resolver>
如果输入参数为T []，则Mule始终调用method1，忽略方法名称。
如果您尝试这样做：
<method-entry-point-resolver>
<include-entry-point method="method1"/>
</method-entry-point-resolver>
<array-entry-point-resolver>
<include-entry-point method="method2"/>
</array-entry-point-resolver>
Mule仍然没有始终调用正确的方法。所以我最终创建了一个简单包装T []的类，并将其更改为method1的输入参数。在array-entry-point-resolvers集合中的method-entry-point-resolvers和method2的集合中配置了method1，这很有效。
这显然是一个问题，但我无法让MuleSoft的人回应。