簡體   English   中英

使用MockExpressionManager進行Camunda Process Engine配置以實現Wildfly

[英]Camunda Process Engine configuration with MockExpressionManager for wildfly

我們已將Camunda安裝為Wildfly8的模塊。 一切正常,但是我需要一種模擬Java委托進行單元測試的方法(使用Arquillian)。 據我了解,org.camunda.bpm.engine.test.mock.Mocks可用於提供模擬的委托。 根據JavaDoc,我應該在我的流程引擎配置中注冊MockExpressionManager。 我在這里找到了與MockExpressingManager類似的配置https://github.com/camunda/camunda-bpm-assert/blob/master/camunda-bpm-assert-examples/src/test/resources/camunda.cfg.xml

但是在standalone-full.xml中配置了適用於wildfly的camunda模塊:

        <subsystem xmlns="urn:org.camunda.bpm.jboss:1.1">
        <process-engines>
            <process-engine name="default" default="true">
                <datasource>
                    java:jboss/datasources/ProcessEngine
                </datasource>
                <history-level>
                    full
                </history-level>
                <configuration>
                    org.camunda.bpm.engine.cdi.CdiJtaProcessEngineConfiguration
                </configuration>
                <properties>
                    <property name="jobExecutorAcquisitionName">
                        default
                    </property>
                    <property name="isAutoSchemaUpdate">
                        true
                    </property>
                    <property name="authorizationEnabled">
                        true
                    </property>
                    <property name="jobExecutorDeploymentAware">
                        true
                    </property>
                    <property name="expressionManager">
                        org.camunda.bpm.engine.test.mock.MockExpressionManager
                    </property>                     
                </properties>

但這不起作用,在Wildfly啟動上,我看到了

16:45:31,930 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 61) MSC000001: Failed to start service org.camunda.bpm.platform.process-engine.default: org.jboss.msc.service.StartException in service org.camunda.bpm.platform.process-engine.default: org.camunda.bpm.engine.ProcessEngineException: Could not set value for property 'expressionManager' on class org.camunda.bpm.engine.cdi.CdiJtaProcessEngineConfiguration
    at org.camunda.bpm.container.impl.jboss.service.MscManagedProcessEngineController$1.run(MscManagedProcessEngineController.java:97)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_11]
    at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_11]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_11]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_11]
    at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_11]
    at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
Caused by: org.camunda.bpm.engine.ProcessEngineException: Could not set value for property 'expressionManager' on class org.camunda.bpm.engine.cdi.CdiJtaProcessEngineConfiguration
    at org.camunda.bpm.container.impl.metadata.PropertyHelper.applyProperty(PropertyHelper.java:76)
    at org.camunda.bpm.container.impl.metadata.PropertyHelper.applyProperties(PropertyHelper.java:94)
    at org.camunda.bpm.container.impl.jboss.service.MscManagedProcessEngineController.startProcessEngine(MscManagedProcessEngineController.java:173)
    at org.camunda.bpm.container.impl.jboss.service.MscManagedProcessEngineController$2.run(MscManagedProcessEngineController.java:131)
    at org.camunda.bpm.container.impl.jboss.service.MscManagedProcessEngineController$2.run(MscManagedProcessEngineController.java:129)
    at org.camunda.bpm.container.impl.jboss.util.Tccl.runWithTccl(Tccl.java:53)
    at org.camunda.bpm.container.impl.jboss.util.Tccl.runUnderClassloader(Tccl.java:45)
    at org.camunda.bpm.container.impl.jboss.service.MscManagedProcessEngineController.startInternal(MscManagedProcessEngineController.java:129)
    at org.camunda.bpm.container.impl.jboss.service.MscManagedProcessEngineController$1.run(MscManagedProcessEngineController.java:90)
    ... 6 more
Caused by: java.lang.IllegalArgumentException: argument type mismatch
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_11]
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_11]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_11]
    at java.lang.reflect.Method.invoke(Method.java:483) [rt.jar:1.8.0_11]
    at org.camunda.bpm.container.impl.metadata.PropertyHelper.applyProperty(PropertyHelper.java:74)
    ... 14 more

如何正確地將此MockExpressionManager設置為配置?

還是可能有其他模擬Java委托的方法?

通過查看Camunda代碼,他們期望傳遞對表達式管理器的引用。如果我不得不猜測,這將作為字符串傳遞。 我可以想到的一種骯臟的方法是創建CdiJtaProcessEngineConfiguration的子類,該子類配置適當的表達式管理器,將該JAR部署到其模塊中並將其CdiJtaProcessEngineConfiguration

就我個人而言,我發現在直接Wildfly集成中它們的配置對我來說太緊了,因此選擇直接在我的應用程序中配置它們的庫。

暫無
暫無

聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.

 
粵ICP備18138465號  © 2020-2024 STACKOOM.COM