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.

Bug 161138 - Integrate a debugger with compapp project
Summary: Integrate a debugger with compapp project
Status: NEW
Alias: None
Product: soa
Classification: Unclassified
Component: Composite Application (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Venkat Chellasamy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-25 14:06 UTC by Nikita Krjukov
Modified: 2009-03-25 15:10 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nikita Krjukov 2009-03-25 14:06:57 UTC 
It would be helpful to be able debugging messages between different JBI components. The CASA editor looks like a good
candidate of debugging UI. It can be used for setting new breakpoints and tracking complex process execution state. 

Now we have BPEL debugger and it works perfect. But sometimes it's necessary to know what happens outside of BPEL.
Comment 1 Kirill Sorokin 2009-03-25 15:10:26 UTC 
It's important to note that this is no easy task, as there is essentially nothing to _debug_ in a composite application,
since unlike BPEL there is no execution _flow_. We will have a debugger in Fuji, which does have a message flow. For
comp app in its current form we could possibly allow monitoring messages going in/out of endpoints, but that would not
be real debugging.