[jbosstools-issues] [JBoss JIRA] (JBIDE-22227) Hotcode replace fails on local wildfly if breakpoint is set

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199819#comment-13199819 ] 

Max Rydahl Andersen commented on JBIDE-22227:
---------------------------------------------

where does eclipse gain a reference ? so far my understanding is that it does not have a reference but tat when asking the debugger to replace classes it does it on *all* classes including old classes not yet garbage collected.

If you say bug is caused by eclipse does that imply that this does not behave the same way using netbeans or intellij ?

> Hotcode replace fails on local wildfly if breakpoint is set
> -----------------------------------------------------------
>
>                 Key: JBIDE-22227
>                 URL: https://issues.jboss.org/browse/JBIDE-22227
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.4.0.Alpha1
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 4.4.0.Alpha1
>
>
> When debugging a local wildfly server with a deployed servlet, making a breaking change such as method name or signature will fail. 
> This will pop up a dialog asking to restart the module or the server,  which is expected. However, after that,  non-breaking changes will still also pop up the hotcode-failed dialog, when it shouldn't. 
> Workflow:
>    1) Create a dynamic web project with simple servlet
>    2) Start a wildfly 10 in debug mode and deploy the web project
>    3) Run-on-server the servlet object and verify it shows expected output
>    4) Set a breakpoint inside the doGet() method
>    5) refresh browser (breakpoint gets hit),  press play
>    6) Make a non-breaking change (change text inside doGet())
>    7) refresh website, verify breakpoint is hit, website content is updated
>    8) make a breaking change by adding a new method
>    9) hotcode-replace dialog appears.  Press 'restart module'
>    10) refresh web browser, verify breakpoint is hit, output has changed as expected
>    11) make a non-breaking change in output of doGet()
>    12) ASSERT:  hotcode replace dialog does NOT show  - THIS STEP FAILS



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)