topic Re: Problem with field injection with Spring proxy in Alfresco Forum

Problem with field injection with Spring proxy

brendenr — Wed, 22 Feb 2017 17:49:37 GMT

Hi, I am trying to use field injection on a JavaDelegate service and am having an issue with Spring where activiti is trying to get/set the field on the service object but Spring is proxying that object (via JdkDynamicAopProxy) and activiti can't find the field through the proxy.The XML for the serv

Re: Problem with field injection with Spring proxy

thuynh — Fri, 24 Feb 2017 07:34:36 GMT

Hi Brenden R .

Could you make a unit test to share? It's unclear why Proxy was called instead of the CorrelationService service task. How do you configure and setup Activiti?

My unit test for injected fields on service task works as expected.

Thanks,

Thong Huynh

‌

Re: Problem with field injection with Spring proxy

brendenr — Fri, 24 Feb 2017 14:17:24 GMT

I believe it is being proxied as part of AoP in the Spring framework. Surely Activiti is compatible with Spring? Strangely enough, a unit test using a mocked rest object seems to not cause any problems, it's only when I run the full web application that the proxy issue is arising -- perhaps an artifact of the way Spring handles unit tests, I'm really not sure. Either way, this is a pretty basic Activiti use case that it seems hard to believe wouldn't be possible in conjunction with Spring. Maybe there is some kind of configuration issue or something?

Re: Problem with field injection with Spring proxy

thuynh — Fri, 24 Feb 2017 16:24:03 GMT

Hi Brenden R ,

Interesting! We have used Java service task's field injection in actual web applications deployed on application server and we haven't seen this issue. From your description, it seems that you are implementing Spring AOP in your application. That actually makes sense as it sort of matches to the error you're having.

Field definition uses unexisting field 'correlationName' on class com.sun.proxy.$Proxy143] with root cause

Did your unit test include AOP parts as well? Perhaps you actually did create a proxy to intercept the java service task? Anyway, it's all wild guesses from me for now. It would be great if you can reproduce the issue within a unit test and share. If you use AOP, please try to include it to the unit test as well. Also, if you can share your beans.xml file, that would be useful as well.

Thanks,

Thong

‌