topic Re: Injecting class in (JAVA) serviceTask manually for testing in Alfresco Archive

Injecting class in (JAVA) serviceTask manually for testing

sruiz — Wed, 15 Dec 2010 11:59:17 GMT

Is it possible to inject manually in the service task the class for testing purposes?As I read, the JavaDelegate object is injected in the process definition first time the process is instanced.The problem is that I would like to inject a RuntimeService component (the runtimeService from the Activit

Re: Injecting class in (JAVA) serviceTask manually for testing

frederikherema1 — Wed, 15 Dec 2010 13:58:43 GMT

Hi,

If your goal is to use the RuntimeService from within your JavaDelegate implementation, then you should rethink this

The API is created to be used outside of the process-context. When you will try to use a service (eg. runtimeService) in the JavaDelegate, transactions an command-context will be messed up.

Re: Injecting class in (JAVA) serviceTask manually for testing

sruiz — Thu, 16 Dec 2010 07:40:26 GMT

I agree that a rule of thumb should be

Don't change process flow with code, use only process variables

.

I didn't want to change flow using runtimeService. I only wanted to access to parent process variables within a subprocess using ProcessInstanceQueries.

Execution class should access to parent variables or a best solution: access to parent execution. Currently I can not.

I only try to find a temporary solution to:
http://jira.codehaus.org/browse/ACT-313
http://jira.codehaus.org/browse/ACT-354

:cry: Excuse me, maybe the question shall be in other topic:

Access to parent variables within a sub-process with code

.
If you want I open a new topic with this issue.

Re: Injecting class in (JAVA) serviceTask manually for testing

frederikherema1 — Fri, 17 Dec 2010 14:02:07 GMT

Ah, now I see. A workaround could be to use the activiti-sessions instead of API to get execution-variables from parent, eg:


CommandContext
      .getCurrentSession(RuntimeSession.class)
      .findVariableInstancesByExecutionId(parentExecutionId);

or

CommandContext
      .getCurrentSession(RuntimeSession.class)
      .findExecutionById(parentExecutionId);

Since this is not part of the public API, we can't guarantee that the method-signature (or method itself) will remain the same over time. Also note that this code will only work when invoked from within a process-context (eg. taskListener or JavaDelegation).