I asked a question on the list the other week about the fail method not being callable during startup - any idea? I've got a patch ready...
Previous message: Hi list, I've been looking at this fail method on DaemonController and it looks like it is for giving a slightly friendlier error message back to the console, rather than a stack trace. I was hoping I could use this to report error messages during initialisation, but it looks like that is not the case. I've noticed that the implementation in DaemonLoader doesn't allow it before the daemon has started up, which seems odd to me as that seems like the time you are most likely to want to fail with an error message. Is this a bug, or is there some reason why it checks isAvailable before it lets you call fail? On Mon, Sep 27, 2010 at 10:48 AM, Mladen Turk <mt...@apache.org> wrote: > Hi, > > > I plan to T&R Daemon 1.0.4 this week > There are couple of minor and one major (DAEMON-100) > fixes resolved in the SVN. > > > Comments? > > Regards > -- > ^TM > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
