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.
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.
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.
assigning to Ling for clarification.
-> Sierra
Changed target milestone from Sierra to 6.1 in order to display correct info on NB 6.1 dashboard
This is already fixed. I just forgot to update the issue.>
tested and verified using 11/24 build and was able to debug and do stepping/breakpoints on Alarm and onMessage.