We recently converted from RSA 6 to RSA 220.127.116.11. In the previous version, we used to be able to run the jsp/web application in debug mode, and make java code changes on the fly. Usually, after the changes, the debug mode would reset and go back to the beginning of the method it was stepping through and allow us to step through the method again, with the new code in place. With the new RSA version, this almost never happens. We usually get a message window that says, "Obsolete Methods on the Stack: Websphere Application v6.1 localhost:7777 contains obsolete methods. Reason: The virtual machine was unable to remove all stack frames running old code from the call stack. The virtual machine is not supplying the debugger with valid data for those frames. Stepping into these obsolete frames may be hazardous to the target virtual machine." Now we have to stop and re-start the server in order to debug with the revised code, which is very inefficient.
Also, with the previous RSA version, when we made changes to our jsp pages, we could usually delete the compiled .class files where the temporary server files are stored under the server node in Windows Explorer. We could then just refresh the browser (Internet Explore v6), and the application would recompile the class files, and we would see the effects of our jsp file changes on the screen. Now, even after deleting the class files as we were doing before, we still have to stop and re-start the server in order to see the changes take effect. Again, very disruptive to our work.