topic Not able to inject Beans in listeners in Alfresco Archive

Not able to inject Beans in listeners

viral — Fri, 24 Jun 2011 12:23:19 GMT

Hi, I have created one usertask with form. I have configured listener to that task. I have used Spring JPA. When i am submitting that form control comes to that listener but that listener not able to inject @PersistenceContext to EntityManager.Can any one help how could i configure my spring con

Re: Not able to inject Beans in listeners

jbarrez — Mon, 27 Jun 2011 07:27:45 GMT

Did you set the required Spring scanner for @PersistenceContext support ?
<bean class="org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor" />

Re: Not able to inject Beans in listeners

viral — Mon, 27 Jun 2011 09:19:01 GMT

It is also not working after adding Spring scanner for @PersistenceContext. It is working w/o Spring scanner for @PersistenceContext when i am working JUNIT. But is not woking when i an relacing activiti.cfg.xml in rest application

Thanks,
Viral

Re: Not able to inject Beans in listeners

jbarrez — Mon, 27 Jun 2011 09:34:07 GMT

How are you replacing the activiti.cfg.xml in the REST app? Do you change the spring config manually there?

Re: Not able to inject Beans in listeners

viral — Mon, 27 Jun 2011 10:03:28 GMT

No, I am creating activiti-cfg.jar for my activiti.cfg.xml and then Relacing the activiti-cfg.jar .

Re: Not able to inject Beans in listeners

jbarrez — Mon, 27 Jun 2011 10:16:30 GMT

A regular activiti.cfg.xml doesnt have Spring support, so thats why it doesnt work.
You need a 'real' spring-Activiti config to make it work.

Re: Not able to inject Beans in listeners

viral — Mon, 27 Jun 2011 10:35:25 GMT

Thanks,
But I have configured that as given in user guide. So where do i get help for 'real' spring-Activiti.

Re: Not able to inject Beans in listeners

jbarrez — Tue, 28 Jun 2011 09:38:33 GMT

To be more precise: the activiti-rest webapp uses a Spring appliation context to configure itself.
The engine however, is not configured in Spring. There is an activiti.cfg.jar placed on the classpath, containing a process engine configuration for which the engine is called 'default'.
The process engine is then referenced in the Spring context using the 'default' name.

If you want to tweak the activiti-rest webapp, and you want to use Spring you'll have to
- remove the activiti.cfg.jar or any other activiti.cfg.xml on the classpath
- add your process engine configuration to the applicationcontext (webapplicationtext.xml) of the activiti-rest webapp.