[copenhagen]

i think it will be a great shortcut. 😳

[Scott Anderson]

Probably so. Just out of curiosity do you find yourself needing to restart often? What is causing that? The reason I’m asking is that server restarts are rather time-consuming so if there is an issue that we could address that wouldn’t require a restart perhaps we could help out there too. With an exploded deployment model, there should be less need of full server restarts than without. Just curious.

–Scott
MyEclipse Support

[Jon Nermut]

I agree that a “restart” option would be useful.
The reason why I tend to have to restart every so often is that OC4J is a flaky piece of crap 😉 and tends to screw up after a few hot deploys (don’t know why, maybe a memory leak?). A stop/start tends to fix all manner of strange behaviour.

[drewmca]

There are certain things that a hot-deploy can’t deal with. If you have components configured in your app that are initialized at startup or lazy-initialized (e.g., an authorization service), changes to their configuration may get pushed over to an exploded deployment, but there’s no way to get the component to reload the configuration. You can push over Java code changes and get the hot-deploy server to reload compiled code, but custom components don’t have the same luxury. I make config changes at least as often as I make java code changes, and it requires a restart.

[Author]

Posts