Bug 150042 - Bean not instantiated error given if the init string returns a null.
Summary: Bean not instantiated error given if the init string returns a null.
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: VE (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Joe Winchester CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 150013
  Show dependency tree
 
Reported: 2006-07-07 15:52 EDT by Richard Kulp CLA
Modified: 2011-06-13 11: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 Richard Kulp CLA 2006-07-07 15:52:23 EDT 
Currently if the init string returns a null we say that the bean was not instantiated. We should be able to handle a null also. The problem is that we normally use null value for a setting instead of an IJavaInstance for null. But that only works if we have an exact null as the init string in the parsing. But the string could evaluate to null. That should be valid too.

This could be a problem. Need to check what would happen if we have a IJavaInstance but its proxy is null.
Comment 1 David Williams CLA 2007-09-19 15:12:14 EDT 
As part of some general bugzilla cleanup, I am marking all old JEM bugs as "won't fix" simply because JEM is in maintenance mode, and there are no plans to fix these old bugs. 

If I have mistaken marked something that is still a current problem in the latests releases from WTP, please re-open.
Comment 2 Philippe Ombredanne CLA 2007-09-20 18:50:08 EDT 
Moving back to VE.