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.
Steps to reproduce: - create Sync sample process - select Composite Application, invoke Debug Project in the context menu - the project will be deployed, debug session will start, user will be able to debug the project - create ASync project - deploy the ASync project - set some breakpoints - try to debug it by running tests - debugger will not stop at the breakpoints User has to restart debug session to make ASync project debuggable (project redeployment is not required). This bug does not happen if you start debug session: any deployed project can't be debugged
Sorry! Please read the last sentence as This bug does not happen if you start debug session: any deployed project _CAN_ be debugged
This is really an expected behaivor: - if user starts debug session by using "Debug Project (BPEL)" context menu item of CompApp project - that means that he's interested in that particular project ONLY and that during the created debug session he'll be able to debug only those BPELs which are included in the selected CompApp. The name of a debug session in that case is a name of CompApp project plus " (BPEL)"; - if user starts debug session by using "Attach Debugger..." menu item - that means that the user is interested in debugging the whole BPEL engine. The name of a debug session would be smth like "localhost:3343". This behaivor is enforced and, what may be more important, can be changed by user by the means of "Sources View". User can check those sources that he wants to debug during current debug session.
verified