It is very frustrating to stop the server and start the server for any small changes made in the application.
Is developer supposed to restart the server for for any small changes made along with the testing?
One restart(Stop and Start) activity takes more than 10-15 mins. in debug mode.
1) I make some changes then I start server in debug mode
2) I see some mistakes in my bean code
3) I change my bean.java or Impl.java
4) I make a futile effort to reload Jars and reload the page
5) It never takes my changes
6) Only changes in properties of jspx components will accept the changes at the page refresh
6) I add new component or new binding to jspx page, This will not even pay heed to re-deployment, I need restart the server
7) I work only 7 hrs a day (1 hr-lunch)! 7*60=420 mins.... lets say I make code changes 10 times a day 10*20(200) half day
is gone in just restarting server/redeploying changes.
8) So frustrating..... !!!
Que:
1) Is the developer is supposed to imagine all the errors beforehand and code so that he wont waste time in restarting?
2) How nice it would be that you just recompile the changes and you get to see your changes just by refresh...
that is why pl/sql development is so fast.
3) Is there any way to do it like that? or Are there are any quick tricks or precautions to avoid restarting the server.
4) Am I not following the correct development/deployment methods?
It will be really great help for me if you experts guide me on the practise you follow for restarting/redeploying.
Thanks
Rahul