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 251474 - Warning "add method not implemented" even after redeploy
Summary: Warning "add method not implemented" even after redeploy
Status: REOPENED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 8.1
Hardware: PC Linux
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-28 16:47 UTC by everflux
Modified: 2015-04-03 17:36 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description everflux 2015-03-28 16:47:52 UTC
I have a maven based web application, deployed in tomcat, that is running under netbeans debugger.

After adding a method I got the message "The debugger does not support Hot Fix action. details: add method not implemented".
A redeploy is happening then.

After clicking 'ok' and performing code changes inside a different method, this time not adding a new method, the warning appears again.

After restarting the debugging session the same edit does not yield the warning dialog, but a redeploy happens nevertheless. (This may be intended by deploy-on-save)
Comment 1 Martin Entlicher 2015-04-03 15:28:40 UTC
It's better to use redeploy then hotfix, since the hotfix has limitations.
Hotfix always tries to redefine the whole class, therefore when you add a method, then even when you make further changes to method bodies, the added method is a part of the class that is being redefined.

The redefinition logic is implemented in the debugger backend in JDK.
Comment 2 everflux 2015-04-03 16:29:14 UTC
The error message should not appear on every change in the same debugging session when problematic situation is resolved by a redeployment. (In this case netbeans triggers a redeploy after the user clicked ok. All future changes trigger the warning, this time without redeployment, again.)
Comment 3 Martin Entlicher 2015-04-03 17:36:13 UTC
O.K. I'll check the behavior...