When this happens bounce the server and the code will be picked-up. The server will probably not be able to pickup your hotswapped changes so the server will continue to run the old code If the project is OK RAD will deploy your changesģ. If unable to do a hot swap correctly you need to bounce your server.įor example, if you have RAD setup to automatically build, your server is running, and you change an EJB what will happen is:Ģ. Hot swaps work well for some things (such as JSPs) but not as well for other things (configuration files, EJBs, etc). When you (or your IDE via the commands above) does a 'publish' it takes all of your compiled objects and deploys them onto the server that you've setup for this project (via a hot swap if the server is running). When you 'build all' it builds all objects then does a 'publish'. When you 'build' it builds anything it thinks is necessary then does a 'publish'. When you 'clean' it gets rid of the compiled objects and recreates them via a 'build all' then does a 'publish'.
0 Comments
Leave a Reply. |