[ https://issues.jboss.org/browse/JBIDE-26147?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-26147. --------------------------------- Resolution: Done Incremental deployment is not guaranteed to work when method signatures are added or removed. When the server is started in 'run' mode, this will simply change the .class file. WildFly is not looking for changes to .class files when in run mode. Incremental deployment when in 'run' mode only really affects static files like html, css, js, etc. When in debug mode, incremental deployment will copy the changed files (as in run mode) except the attached remote debugger will automatically update the running code. If a method signature changes, it may or may not work depending on the situation. Often times you'll get a hotcode replace error. In both of these situations, the proper solution is to right-click on the module in the servers view and select full publish. tl;dr, Incremental deployment has limitations. It is not magic and cannot work if the server is not looking for changes (run mode), or the changes cannot possibly be made (hotcode replace error in debug mode). In all cases, if your deployment seems broken, execute a full publish on it to fix it. I tested this scenario. This scenario can be split into 2 problems: 1) Why is the getEvent method failing via classnotfoundException 2) Why, when re-commented, does the deployment not go back to normal? Item 1 is due to wildfly having a lower version of jaxrs that does not have these classes. I / we cannot fix that here. Item 2 was discussed above. Full publish makes it work again. Marking as closed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)