Ticket #14 (closed enhancement: fixed)
Displaying Thrown Exception in Tool Info View
Reported by: | sensoria | Owned by: | sct |
---|---|---|---|
Priority: | minor | Milestone: | IntegrationVersionM30 |
Component: | SDE GUI | Version: | |
Keywords: | exception, tool | Cc: | mtribast@inf.ed.ac.uk |
Description
I am providing PEPA tools to the Sensoria CASE Tool. One of my functions throws a checked exception. Would it be possible to enrich the Tool Info tab with information about checked exceptions? Also, it would be nice to let the API developer declare unchecked exceptions used, for instance, to validate the arguments (this would be in the style of the javadoc conventions for the 'throws' keyword).
Change History
comment:2 Changed 10 years ago by sct
- Owner changed from mayer to sct
- Status changed from new to assigned
I will look into this.
comment:4 follow-up: ↓ 5 Changed 10 years ago by mayer
- 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.
comment:5 in reply to: ↑ 4 Changed 10 years ago by anonymous
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.
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)