You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Kenneth Tam (JIRA)" <be...@incubator.apache.org> on 2005/02/16 23:32:50 UTC

[jira] Assigned: (BEEHIVE-209) Need ability to log warnings, errors etc for controls assembly

     [ http://issues.apache.org/jira/browse/BEEHIVE-209?page=history ]

Kenneth Tam reassigned BEEHIVE-209:
-----------------------------------

    Assign To: Kenneth Tam

Yes, this would definitely be useful.


> Need ability to log warnings, errors etc for controls assembly
> --------------------------------------------------------------
>
>          Key: BEEHIVE-209
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-209
>      Project: Beehive
>         Type: Bug
>   Components: Controls
>     Versions: V1Beta
>  Environment: Windows
>     Reporter: Lawrence Jones
>     Assignee: Kenneth Tam

>
> Currently if something goes wrong or you want to warn the user of something in assembly you have 2 choices:
> 1. write directly to System.out or System.err
> 2. raise an exception
> At the moment all exceptions are caught in Assembler.assemble(). A stack trace is written to stderr but the exception is not rethrown so AssembleTask looks as though it finishes successfully.
> But if that is fixed there is no way to raise a warning or information message without either stopping assembly completely or writing to stdout or stderr directly.
> We should provide a Logger interface available via the assembly context to which you can log errors, warnings and info messages at least. And we should provide an implementation of this interface which can be used by default in the AssembleTask.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira