Do I really need to reboot JBoss each time I deploy packages

[single]

"single" wrote:
I have noticed that if I deploy new JARs to JBoss that contain bug fixes or new Servlets, those do not become available unless I restart JBoss. I figure this is becasue of some cache settings that are on maybe?

When I am debugging, the constant rebooting takes tons of time. Is there anything I can do so that JBoss completely reloads all classes and loads the most recent ones when I redeploy so that I don't need to constantly restart JBoss when I debug?

[darranl]

"darranl" wrote:
Can you describe what you mean by 'deploy new jars to JBoss', where do you put them?

Also are any messages displayed in the console for redeployment?

[luke_t]

"luke_t" wrote:
If you're talking about EJB jars, or other stuff in the deploy directory, then redeploying will cause the classes to be reloaded. If you mean jars in the lib directory, then you have to reboot.

Luke.

[single]

I am talking about hot deployment into the default deploy directory.

I have several JARs with classes in one JAR referring to classes in another. One I reload one of them, it seems like the links are broken between classes in the JARs that remained unchanged and the JAR that was redeployed.