This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
The debugger plugin cannot determine what process instances may already be running in the BPEL engine. It can only determine what process instances have been started since the debugger was attached. The Process Instance Window should show ALL process instances, including those that may already be running in the BPEL Service Engine.
It looks like that it's already implemented on the runtime side: When debugging session is being established the BPEL Engine sends notifications (enterFrame) for all the process instances the are currently running. This results to all the process instance are visible in the BPEL Process Instances View. So, closing as Fixed.
Reopening the issue. It's found out that enterFrame() are sent for those process instances that was started during some debug session (see my previous comment), not neccesseryly during the current one. So, process instances started when no debug session was established with the BPELSE would not appear in BPEL Process Instances view.
This issue depends on the BPELSE issue #6493548 filed in bugster
It's really a defect
Will look at this after NB 6.0
-> FIXED Though it's hard to predict results of trying to debug a process instance that was already running at the time debugger session was started. Let's try and see what happens.
verified in NetBeans IDE Dev (Build 200802140010)