How to use/bind the DeploymentService in the CDI environment in jBPM 6.2

[awizenm]

I miss another piece of the puzzle.

In my CDI based application the execution of the process fails probably because of still misconfigured environment.

Meanwhile I mange to start my process in my application. The first task is created. To complete the task I use UserTaskService (as suggested by Jimmy in https://developer.jboss.org/thread/255891)

Unfortunately the injected UserTaskService is not able to complete the task because it is not able to find a RuntimeManager for the task (see the complete implementation in UserTaskServiceImpl). This is because the deployment service is not aware of my process???

Why is the process unknown to the deployment service?

Is there a bug in the RuntimeEnvironmentBuilder? Or is it a feature?

This is how I produce the RuntimeEnvironment:

@Produces
@Singleton
@PerRequest
@PerProcessInstance
public RuntimeEnvironment produceEnvironment(EntityManagerFactory emf) {

    Environment env = EnvironmentFactory.newEnvironment();
    env.set(EnvironmentName.TRANSACTION_MANAGER, new ContainerManagedTransactionManager());
    env.set(EnvironmentName.ENTITY_MANAGER_FACTORY, emf);
    
    JpaProcessPersistenceContextManager jpaProcessPersistenceContextManager = new JpaProcessPersistenceContextManager(env);
    JPATaskPersistenceContextManager jpaTaskPersistenceContextManager = new JPATaskPersistenceContextManager(env);

    env.set(EnvironmentName.PERSISTENCE_CONTEXT_MANAGER, jpaProcessPersistenceContextManager);
    env.set(EnvironmentName.TASK_PERSISTENCE_CONTEXT_MANAGER, jpaTaskPersistenceContextManager);

    RuntimeEnvironment environment = RuntimeEnvironmentBuilder.Factory.get()
            .newDefaultBuilder()
            .userGroupCallback(userGroupCallback())
            .addEnvironmentEntry(EnvironmentName.TRANSACTION_MANAGER, new ContainerManagedTransactionManager())
            .addEnvironmentEntry(EnvironmentName.TASK_PERSISTENCE_CONTEXT_MANAGER, jpaTaskPersistenceContextManager)
            .addEnvironmentEntry(EnvironmentName.PERSISTENCE_CONTEXT_MANAGER, jpaProcessPersistenceContextManager)
            .entityManagerFactory(emf)
            .registerableItemsFactory(factory)
            .addAsset(ResourceFactory.newClassPathResource("myProcess.bpmn"), ResourceType.BPMN2).get();

    return environment;
}

By the way: there are no problems with execution of the same process in the test class based on JbpmJUnitBaseTestCase

Any suggestions?

[frenky1983]

See this

https://jsvitak.wordpress.com/2015/01/20/upgrade-of-jbpm-6-examples-to-jbpm-6-2-services/comment-page-1/#comment-259

[awizenm]

Thank you Francesco,

I slowly recognize that loading the process definition form the class path (the RuntimeEnvironment approach) is either broken or simply not supported in jBPM 6.2. The preferred way of dealing with process definitions should be the kjar approach. Right?

The irritating thing about this is that the 6.2 documentation still suggests producing of  RuntimeEnvironment : http://docs.jboss.org/jbpm/v6.2/userguide/jBPMIntegration.html#d0e19365

It is really a waist of time if it is not supported any more.

Michael

[frenky1983]

I follow the line suggest in util package of that example and all work fine for me; there you can find the manner to produce the environment

[swiderski.maciej]

Michael Awizen wrote:

Thank you Francesco,

I slowly recognize that loading the process definition form the class path (the RuntimeEnvironment approach) is either broken or simply not supported in jBPM 6.2. The preferred way of dealing with process definitions should be the kjar approach. Right?

The irritating thing about this is that the 6.2 documentation still suggests producing of  RuntimeEnvironment : http://docs.jboss.org/jbpm/v6.2/userguide/jBPMIntegration.html#d0e19365

It is really a waist of time if it is not supported any more.

it is supported when you use directly RuntimeManager API. Though services provide much more capabilities and thus is the recommended way of loading process definitions (and not only that). With read up from classpath you loose the dynamic behavior so you can deploy/undeploy without restarting application or application server.

HTH

[awizenm]

Hi Maciej,

I have adopted the RuntimeManager example from this great article http://www.mastertheboss.com/jboss-jbpm/jbpm6/jbpm-6-web-application-example to run on WildFly 8.2, JDK 1.8 and jBPM 6.2.

Unfortunately the process execution gets stuck after the first user task. There are no exceptions, no warnings. There is just no execution after the first task is completed. This was also the case in my own application based on the RuntimeManager approach. So I guess there is bug in the underlying engine...

Please see the adopted example project:

[swiderski.maciej]

Michael,

the issue is that there is no listener registered for handling notifications about completed tasks. So to resolve that add following method into CustomApplicationScopedProducer class:

  @Produces

  public TaskLifeCycleEventListener produceTaskListener() {

      return new ExternalTaskEventListener();

  }

with that you should be able to see other tasks moving forward after human task is completed

HTH

[awizenm]

Great, adding the suggested TaskLifeCycleEventListener producer to the producer class solves the issue!

Thank you Maciej!