topic Re: Spring bean cannot be resolved in activiti:delegateExpression in Alfresco Archive

Spring bean cannot be resolved in activiti:delegateExpression

rohitjain — Wed, 29 Oct 2014 19:16:59 GMT

I've this Java based spring configuration file:@Configurationpublic class WorkflowConfig { @Bean public DataSource activitiDataSource() { DriverManagerDataSource dataSource = new DriverManagerDataSource(); dataSource.setDriverClassName("com.mysql.jdbc.Driver"); dataSource.setUrl("

Re: Spring bean cannot be resolved in activiti:delegateExpression

rohitjain — Wed, 29 Oct 2014 19:19:02 GMT

Oh, and I've this simple test class which I'm running, and getting those logs:

<code>
@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(classes= { WorkflowConfig.class, WorkflowServiceTest.Config.class } )
public class WorkflowServiceTest {

@Configuration
public static class Config {

@Bean
public TicketService ticketService() {
   return new TicketServiceImpl();
}

@Bean
public TicketDao ticketDao() {
   return new TicketDaoImpl();
}
}

@Autowired
private WorkflowService workflowService;

@Autowired
private ProcessEngine processEngine;

@Test
public void testGetProcessInstance() {
processEngine.getRuntimeService().startProcessInstanceByKey(
    "invoiceGenerationProcess", variables);
ProcessInstance processInstance = workflowService.getProcessInstance();

assertEquals("invoiceGenerationProcess", processInstance.getId());
}
}
</code>

Re: Spring bean cannot be resolved in activiti:delegateExpression

trademak — Thu, 30 Oct 2014 15:50:29 GMT

Could you create a unit test showing the issue and create a JIRA issue? That makes it easier for use to fix it.

Best regards,

Re: Spring bean cannot be resolved in activiti:delegateExpression

rohitjain — Fri, 31 Oct 2014 06:47:36 GMT

Well, I got it working by replacing <blockcode>ProcessEngine</blockcode> bean with <blockcode>ProcessEngineFactoryBean</blockcode> bean. And then I got the process engine using the <blockcode>getObject()</blockcode> method:

<code>
@Bean
@DependsOn({ "processEngineConfiguration" })
public ProcessEngineFactoryBean processEngineFactoryBean() {
ProcessEngineFactoryBean factoryBean = new ProcessEngineFactoryBean();
factoryBean.setProcessEngineConfiguration(processEngineConfiguration());

return factoryBean;
}

@Bean
public HistoryService historyService() throws Exception {
return processEngineFactoryBean().getObject().getHistoryService();
}
</code>

But to my surprise, the autowiring of <blockcode>ProcessEngine</blockcode> still worked. How? I didn't register that bean anymore now. And what could be the difference that this worked, and <blockcode>buildProcessEngine</blockcode> didn't?

Shall I still raise a JIRA issue? The test is anyway there in the first posting.

Re: Spring bean cannot be resolved in activiti:delegateExpression

jbarrez — Fri, 31 Oct 2014 15:50:13 GMT

Spring knows enough about FactoryBeans to understand what's going on, thats why the wiring works.

However, your first config looks ok, must be something small, cause it should work that way