Bug 1081187

Created attachment 879133 [details]
screenshot

Marek, which project are you using for this?  Note that the process instances view currently only shows process instance that are in memory, so when using persistence (where process instances will be stored in the database at the end of each command), the process instances view will be empty in between calls.

Kris,

I found this issue using the mavenized jBPM Project.

Steps:
1) Create 'jBPM project (Maven)'
2) Add a break point into the generated Java code
3) In the 'variables' view of the Debug perspective select 'ksession'.
4) Switch to the Process Instances view for example.

I suspect this will be the case for the plain 'jBPM project' too. I will try to make sure.

Yep - it's the same. Doesn't even matter weather I use debug as 'drools junit test' or just 'junit test'.

Marek,

I just tried with 6.0.1.Final and it's working as expected there.

Two important remarks:

(1) to see process instances (between different invocations on the ksession), persistence needs to be turned off, otherwise the process instances will be stored in the db an released at the end of each command, so the view will be empty once you hit the breakpoint

(2) you can only see active process instances (even when not using persistence), as completed process instances are no longer relevant for execution and thus removed

The easiest way to get the process instance view working is: New -> Project -> jBPM Project and in the second wizard page select "a more advanced process using human tasks and persistence".  In the generated ProcessTest constructor, change the super constructor to super(true, false) to turn of persistence and put a breakpoint right after ksession.startProcess(..)

Note that debug as drools junit test is only necessary for enabling drools rule breakpoints (it has no effect when debugging pure jbpm).

While we can look at improvements / enhancements, it seems the view is working as expected though.

OK - this is my fault - I've been using it the wrong way and did not pay attention to the NOT USE PERSISTENCE part. My apologies.

This works as expected also with the maven type project. All that is required is to change:

RuntimeEnvironmentBuilder builder = RuntimeEnvironmentBuilder.Factory.get()
			.newDefaultBuilder().entityManagerFactory(emf)
			.knowledgeBase(kbase);

to 

RuntimeEnvironmentBuilder builder = RuntimeEnvironmentBuilder.Factory.get()
			.newDefaultInMemoryBuilder()
			.knowledgeBase(kbase);

Thanks Kris!