I had previously a question about the use of Spring beans in services tasks.
But actually I need to use these beans from the Activiti Explorer. The idea is to make a simple production followup GUI for the production team using Activiti Explorer so they can see processes in error and with a user task retry the service tasks which failed.
When I execute a service task implement with a Spring bean from Activiti Explorer, I get again this org.activiti.engine.impl.javax.el.PropertyNotFoundException: Cannot resolve identifier 'myService' as in my previous post.
I had a look at the source code for StartProcessInstanceClickListener, and I see that runtimeService = ProcessEngines.getDefaultProcessEngine().getRuntimeService(); … exactly what would cause this problem as was said in the previous post.
So in short my questions : - is it possible to use Spring beans to implement a service task triggered from the Activiti Explorer as it is currently ? - If yes, what could go wrong in my case ? The code source is available here on dropbox.
ProcessEngines.getDefaultProcessEngine() -> this will also work when the engine is wired in spring. Once ANY engine starts, it get's registered with the ProcessEngines object. The explorer-app engine has no explicit name set (/activiti-webapp-explorer2/src/main/webapp/WEB-INF/applicationContext.xml), so the default is used, effectively exposing it as the default.
So the engine obtained should be the correct one. Every bean you wire in applicationContext.xml, should be available in expressions…
