Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JBoss doesn't automaticaly detecting source code changes

 
hem kumar
Ranch Hand
Posts: 97
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all, recently i have started using JBoss 5.1 mainly for my own work . But i have found out that JBoss doesn't recognize any changes to source code if i do not redeploy the module or restart the server. This is so time taking considering that each deployment or restarting is taking approximately 2 minutes in my system. If there is any workaround like tomcat, which recognizes changes to source codes immediately?? Thank you very much.
 
sachin burange
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello Hem,

JBOSS does detect the changes. what you have to do is

1. put a class files or its jar file in WEB-INF folder of deployment directory.
2. Reload the context adding space in web.xml

Using these two steps you will able to see that application redeployment starting automatically.

 
hem kumar
Ranch Hand
Posts: 97
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i am using JBOSS with either eclipse or Netbeans . Can you please explain me the steps needed to make this hot deployment work in JBOSS through any of the ide? In both the ides, i either have to run the project again or restart the server again to make any changes to work.
 
sachin burange
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I guess in your case just build the project again and refresh the project.
JBOSS should detect the class changes, just try with sys out first.
 
hem kumar
Ranch Hand
Posts: 97
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No, its not working in the way you described. Even i modified the hdscanner-jboss-bean.xml and change the default value to 500 ms , still its not working. Any other solution??
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic