runshell/runjava lifecycle
Steve Loughran <[email protected]> Thu, 21 Sep 2006 12:00:21 +0100
| Newsgroups | gmane.comp.java.smartfrog.devel |
|---|---|
| Message-ID | <[email protected]> |
One thing I am looking at is the RunShell component, that RunJava is based on. This has a couple of interesting features 1. it has its own attributes, "shouldDetach" "shouldTerminate", and "terminateOnFailure". We could also support the new 'standard' sfShouldDetach, sfShouldTerminate and sfShouldTerminateQuietly options 2. it starts the thread under sfDeploy() and not sfStart(). Surely this is wrong? It should do its work under sfStart()? in sfStart(), runshell starts running the commands on the command list, but if you are using the component just to execute a native or java program with no commands, the execution should be delayed until sfStart(), as that is when you know everything else is set up right. We could fix #2 without breaking things by having a flag saying when to start the worker thread. for now, I'm leaving it alone but filing a bugrep. -steve ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV