SDE Service Development Environment: Ticket #14: Displaying Thrown Exception in Tool Info View

version set

sensoria — Tue, 26 Jun 2007 10:19:45 GMT

version set to 3.0

Hi, I also noticed some exceptions when I was developing the prototype plug-in. It would also be useful to add any "caught" exceptions within the Case Tool to the Eclipse error log by default.

Howard (LSS-ICL)

owner, status changed

sct — Wed, 04 Jul 2007 09:57:45 GMT

owner changed from mayer to sct
status changed from new to assigned

I will look into this.

milestone set

mayer — Fri, 10 Aug 2007 11:47:56 GMT

milestone set to IntegrationVersionM30

version deleted

mayer — Fri, 10 Aug 2007 12:07:56 GMT

version 3.0 deleted

Exceptions from tool invocations are already added to the Eclipse error log.

I will look into how to provide better user feedback in the next version, and how to provide exceptions which give feedback on invalid arguments as mirco has suggested.

anonymous — Tue, 23 Oct 2007 15:32:39 GMT

I think the issue is that the exception of the plug-in is not traceable... i.e. the only exception we see is a generic one. Thus, we cannot see what has caused an exception from within the plug-in. Maybe its a simple case of catching this (internally) and throwing a separate error (in the name of the plug-in)?

Thanks, H of ICL.

Replying to mayer:

Exceptions from tool invocations are already added to the Eclipse error log.

I will look into how to provide better user feedback in the next version, and how to provide exceptions which give feedback on invalid arguments as mirco has suggested.

status changed; resolution set

mayer — Sun, 27 Jan 2008 16:24:16 GMT

status changed from assigned to closed
resolution set to fixed

I have added thrown exceptions to the list displayed in the function browser. Also, exception causes are now logged to the Eclipse error log.