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 84478

Summary:	Allow stepping/breakpoints on onAlarm and onMessage elements
Product:	soa	Reporter:	lchang <lchang>
Component:	BPEL Debugger	Assignee:	Kirill Sorokin <ksorokin>
Status:	VERIFIED FIXED
Severity:	blocker	CC:	zgursky
Priority:	P4
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	ENHANCEMENT	Exception Reporter:

Description lchang 2006-09-08 00:27:24 UTC

onMessage or onAlarm are not activities.  However it would be nice to be able 
to set a breakpoint within these elements.

Eventually it would be nice to be able to step through Copy, If, While, 
RepeatUntil, onAlarm, etc.

Comment 1 Alexander Zgursky 2006-10-24 01:14:28 UTC

Lingling, did you mean onAlarm and onMessage elements inside a pick activity or
inside an event handler? I'm not sure what would be the value of being able to
put breakpoints on them since we can always put a breakpoint on the activity
inside them.
Or, well, for onMessage it may be usefull to suspend a process instance BEFORE
the variable/parts are initialized with the data from the incoming message. For
onAlarm it seems the same - to put a breakpoint on onAlarm or on its inner
activity. However, if we'll implement onMessage breakpoints we can consider
implementing onAlarm breakpoints just for consistency.

Comment 2 Michael Frisino 2006-11-20 18:17:03 UTC

assigning to Ling for clarification.

Comment 3 Kirill Sorokin 2007-12-12 14:26:08 UTC

-> Sierra

Comment 4 Andrei Chistiakov 2008-01-17 11:11:02 UTC

Changed target milestone from Sierra to 6.1 in order to display correct info on
NB 6.1 dashboard

Comment 5 Kirill Sorokin 2008-02-22 13:40:49 UTC

This is already fixed. I just forgot to update the issue.>

Comment 6 ggenipudi 2008-11-25 21:33:17 UTC

tested and verified using 11/24 build and was able to debug and do stepping/breakpoints on Alarm and onMessage.