Sure, you could probably do it easily enough. But if you have to support it, you probably won't appreciate having written it. Many times, you'll think the task is pretty simple and straightforward, you'll write it, and implement it.
...and then three weeks later, about 11:30 PM on a Saturday, it'll fail because one of the many special cases possible triggers. And you get a phone call, only to discover "Oh, yeah, the WAR files are on a remote store that was down for maintenance so the deploy didn't occur, so it didn't get deployed properly." So you make the fix, reimplement it and go back to sleep.
When you're managing production processes, there can be more special cases than you care to think about. So if you have to roll your own, think a good bit about handling the problems that will eventually arise, then think some more. But if you can find an off-the-shelf solution that manages the process for you, why not save yourself the trouble?
...roboticus
When your only tool is a hammer, all problems look like your thumb.
In reply to Re^3: Start and Stop JBoss and Websphere servers
by roboticus
in thread Start and Stop JBoss and Websphere servers
by karthik.raju
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |