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.
During my first time using the RequestProcessor class I stumbled over the fact that tasks posted to the default request processor (getDefault()) can not be canceled during their execution. I don't really know why the request processor is designed this way, but in my opinion this information need to be included in the javadoc of the request processor. I include a patch extending the javadoc of the getDefault() method. Sincerely, Patrick Holthuizen
Created attachment 25142 [details] proposed patch v1 (extended the javadoc of method getDefault())
Wrong category.
Thanks for the patch, but the test is not really correct - you can call Task.cancel() and this may turn into Thread.interrupt() if the right constructor of the RequestProcessor is used.
Do you still think your text shall be applied? If so, reopen.
Dear jtulach, I am not quite sure whether I get you right. You point out to use the proper constructor but that's exactly my point also. My goal is to direct a developer to use a contructor if the cancel() functionality is needed. That's why I think some additional information is needed in the docs of the getDefault() method. Sincerely, Patrick Holthuizen
Ok, now it makes sense to me. openide/util/src/org/openide/util/RequestProcessor.java,v <-- RequestProcessor.java new revision: 1.9; previous revision: 1.8