This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 290371 - Exceptions artefact 'extends' field always defaults to java.lang.Exception
Summary: Exceptions artefact 'extends' field always defaults to java.lang.Exception
Status: CLOSED WONTFIX
Alias: None
Product: Tigerstripe (Archived)
Classification: Technology
Component: Core (show other bugs)
Version: 0.5M1   Edit
Hardware: PC Windows Vista
: P3 minor (vote)
Target Milestone: 0.5M0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-24 04:50 EDT by Craig Gallen CLA
Modified: 2012-03-19 09:35 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Craig Gallen CLA 2009-09-24 04:50:57 EDT 
In our use case, we need to be able to define Tigerstripe Exception artefacts with the extends field ="" i.e. an empty value. Our generators will then substitute an injected object for the empty value. This way we can define the root of the exception hierarchy to suit our application. This approach works with the other tigerstripe artifacts; Events, Entities Facades and Datatypes. 

However with the Exception artefact, the value always defaults to java.lang.Exception and further more, if it is manually set so that extends field ="" (an empty value), the next time the editor is opened, it is once again set to java.lang.Exception. This has the added problem that we are not always generating java code and so having a java exception default presents a problem.

We need to be able to set an empty value for the extends field in Exceptions artefacts.
Comment 1 Navid Mehregani CLA 2012-03-19 09:35:51 EDT 
Please reopen if this is still needed.