Stop Jboss from deploying and Undeploying beans on startup a

[ravanih]

Hi all,

I would like to know if it's possible to stop jboss from undeploying beans (ear files) on shutdown, so that they don't have to be deployed on startup.

The reason being, we are currently developing the system and hence we need to start and stop the server again and again, and whenever we do so it has to undeploy about 110 beans and then on startup it goes and deploys them again. This gets annoying as it takes 2 minutes every time to startup.

I tried to search on forums and on google without success. Therefore any help would be greatly appreciated.

We are using Jboss 4.0.1sp1

Thanks,

Regards,
Hiten.

[theute]

You should look at why you need to restart the server, you should not need to do so.

[beyarecords]

Thomas,
i'm having tha same problem. Changes to hibernate xml maps/classes do not take effect unless the server is restarted. What is the issue here?

I am using Jboss 4.0.0 on OS X 10.3.7.

regards

Uzo

[theute]

Redeploying your webapp should be enough.

[ravanih]

Hi,

The reason for the need to restart the server is because as i mentioned earlier , the system is still under development and hence most of the time there are bugs which causes the EAR file to not deploy properly. Without restarting the server if you try to redeploy the EAR file by fixing the bug , Jboss would still complain that there is already an instance registered (Jboss seems to have this problem when there is an incomplete deployment) and would not deploy, unless you restart it.

Regards,
Hiten

[dlmiles]

"ravanih" wrote:
The reason for the need to restart the server is because as i mentioned earlier , the system is still under development and hence most of the time there are bugs which causes the EAR file to not deploy properly. Without restarting the server if you try to redeploy the EAR file by fixing the bug , Jboss would still complain that there is already an instance registered (Jboss seems to have this problem when there is an incomplete deployment) and would not deploy, unless you restart it.

Regards,
Hiten

I've seen this problem too with the JBossDukesBank.ear, this was when I was using the incorrect version of jbossj2ee-src.zip for the startguide40.pdf and down to me trying to manufacturer ejb-jar.xml files that worked (or rather that appeared to work, it shut the build process up but my files were clearly wrong) .

When I corrected the versions of example source and this time the build process generated its own ejb-jar.xml files that problem no longer exists.

I can delete my EAR, or simply overwrite it and JBoss correctly runs a complete undeploy before redeploying again no signs of any already bound name exceptions.