Bug 173338 - [DOM] bindings should be adapted to missing binary type support
Summary: [DOM] bindings should be adapted to missing binary type support
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-07 15:03 EST by Olivier Thomann CLA
Modified: 2019-12-07 14:19 EST (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 Olivier Thomann CLA 2007-02-07 15:03:56 EST 
We might need to check what is the current behavior for the return type of a method binding and the type of a field binding when this type is a missing binary type binding.
The spec doesn't expect null to be returned.
Comment 1 Olivier Thomann CLA 2007-02-07 15:06:42 EST 
In these cases, we might want to return java.lang.Object.
We might also want to prune the interfaces, exception types, type arguments, ... arrays from the null values instead of returning an empty array.
See bug 172633.
Comment 2 Eclipse Genie CLA 2019-12-07 14:19:43 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.