You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Mladen Turk (JIRA)" <ji...@apache.org> on 2010/10/11 00:01:31 UTC
[jira] Commented: (DAEMON-177) Allow fail during init
[ https://issues.apache.org/jira/browse/DAEMON-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919669#action_12919669 ]
Mladen Turk commented on DAEMON-177:
------------------------------------
Daemon has JDK 1.3 as target. Throwable.getCause() is present in 1.4 onwards.
> Allow fail during init
> ----------------------
>
> Key: DAEMON-177
> URL: https://issues.apache.org/jira/browse/DAEMON-177
> Project: Commons Daemon
> Issue Type: Improvement
> Affects Versions: 1.0.3
> Environment: linux
> Reporter: Nick Griffiths
> Priority: Minor
> Fix For: 1.0.4
>
> Attachments: allow-init-fail-via-init-exception.diff, remove-fail-available-check.diff
>
>
> It would be handy to be able to fail with a nice message during init, such as 'database not available' or 'no config file found' or whatever.
> At the moment, if you try that during init, you get an IllegalStateException. I've attached a patch which removes this restriction in DaemonLoader, but failing at this stage doesn't stop the c code from calling start. I could work around this in the DaemonLoader, but not sure that is the right approach. I'll have a go at doing a patch for the c-code, but I'm not a confident in my c skills...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.