Issue 0000362 -- Exception Reporting

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 0000362 -- Exception Reporting

Steve Wartik
I was browsing the bugs on mantis and noticed the request for feature
0000362, in which exceptions will go to the log file and not to stderr.

Maybe I'm reading too much into the one-line description, but for the
time being I want to see exceptions on my console. The OWL plugin, and
for that matter the Protégé core, still isn't all that stable. I
encounter enough uncaught exceptions that I've learned to keep the
console visible so I can glance at it when Protégé doesn't behave as I
expect (usually "click button, GUI doesn't change"). Opening and
reopening the log file would slow me down.

Unless there is also an intent to be more scrupulous about reporting
exceptions in pop-ups, I'd like to request the
Protégé developers go slow on this one.

Steve Wartik

-------------------------------------------------------------------------
To unsubscribe go to http://protege.stanford.edu/community/subscribe.html

Reply | Threaded
Open this post in threaded view
|

Re: Issue 0000362 -- Exception Reporting

Ronnie Valkky
Hi Steve,

I definetely support you in this.

I also keep console opening to see errors and exception.

Could it be more useful to consider systematic approach to be prepared
to exceptions in java code and also to report errors with an unique error
code ?

The good thing is that developers are thinking new solutions.

cheers,
Ronnie


----- Original Message -----
From: "Steven Wartik" <[hidden email]>
To: <[hidden email]>
Sent: Monday, February 13, 2006 9:36 PM
Subject: [protege-owl] Issue 0000362 -- Exception Reporting


> I was browsing the bugs on mantis and noticed the request for feature
> 0000362, in which exceptions will go to the log file and not to stderr.
>
> Maybe I'm reading too much into the one-line description, but for the
> time being I want to see exceptions on my console. The OWL plugin, and
> for that matter the Protégé core, still isn't all that stable. I
> encounter enough uncaught exceptions that I've learned to keep the
> console visible so I can glance at it when Protégé doesn't behave as I
> expect (usually "click button, GUI doesn't change"). Opening and
> reopening the log file would slow me down.
>
> Unless there is also an intent to be more scrupulous about reporting
> exceptions in pop-ups, I'd like to request the
> Protégé developers go slow on this one.
>
> Steve Wartik
>
> -------------------------------------------------------------------------
> To unsubscribe go to http://protege.stanford.edu/community/subscribe.html
>
>


-------------------------------------------------------------------------
To unsubscribe go to http://protege.stanford.edu/community/subscribe.html