功能测试组件的问题（Mule 3.2.1）

我希望

等同于

<component>
    <spring-object bean="FTC" />
<component>

使用FunctionalTestComponent配置Springbean

<mule ...>
    <vm:endpoint name="EntryPoint.Name" path="EntryPoint.Path" />
    <spring:bean id="FTC" class="org.mule.tck.functional.FunctionalTestComponent" />

    <simple-service name="service" endpoint-ref="EntryPoint.Name" >
        <component>
            <spring-object bean="FTC" />
        </component>
    </simple-service>
</mule>

带有

的配置通过测试。但是，有FTC bean的那个没有。事实上，使用FTC bean的运行在日志中显示了一个异常：

********************************************************************************
Message               : Component that caused exception is: DefaultJavaComponent{service.commponent}. Message payload is of type: String
Code                  : MULE_ERROR--2
--------------------------------------------------------------------------------
Exception stack is:
1. null (java.lang.NullPointerException)
  org.mule.tck.functional.FunctionalTestComponent:215 (null)
2. Component that caused exception is: DefaultJavaComponent{service.commponent}. Message payload is of type: String (org.mule.component.ComponentException)
  org.mule.component.DefaultComponentLifecycleAdapter:359 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/component/ComponentException.html)
--------------------------------------------------------------------------------
Root Exception stack trace:
java.lang.NullPointerException
    at org.mule.tck.functional.FunctionalTestComponent.process(FunctionalTestComponent.java:215)
    at org.mule.tck.functional.FunctionalTestComponent.onCall(FunctionalTestComponent.java:108)
    at org.mule.model.resolvers.CallableEntryPointResolver.invoke(CallableEntryPointResolver.java:50)
    + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything)
********************************************************************************

知道我做错了什么吗？我正在使用Mule 3.2.1

---

谢谢

我想我明白了。bean的定义缺少一个属性

init方法=
“初始化”

。这一细节似乎在报告中遗漏了。因此，bean的定义应该是：

<spring:bean id="FTC"
    class="org.mule.tck.functional.FunctionalTestComponent" init-method="initialise" />

---

出于同样的原因，我认为文档中显示的也会失败：（一般来说，无论如何还是使用test:component更好。@David：你说得对。我后来意识到我不需要为自己的目的使用单独的bean。

********************************************************************************
Message               : Component that caused exception is: DefaultJavaComponent{service.commponent}. Message payload is of type: String
Code                  : MULE_ERROR--2
--------------------------------------------------------------------------------
Exception stack is:
1. null (java.lang.NullPointerException)
  org.mule.tck.functional.FunctionalTestComponent:215 (null)
2. Component that caused exception is: DefaultJavaComponent{service.commponent}. Message payload is of type: String (org.mule.component.ComponentException)
  org.mule.component.DefaultComponentLifecycleAdapter:359 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/component/ComponentException.html)
--------------------------------------------------------------------------------
Root Exception stack trace:
java.lang.NullPointerException
    at org.mule.tck.functional.FunctionalTestComponent.process(FunctionalTestComponent.java:215)
    at org.mule.tck.functional.FunctionalTestComponent.onCall(FunctionalTestComponent.java:108)
    at org.mule.model.resolvers.CallableEntryPointResolver.invoke(CallableEntryPointResolver.java:50)
    + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything)
********************************************************************************

<spring:bean id="FTC"
    class="org.mule.tck.functional.FunctionalTestComponent" init-method="initialise" />