| Summary: | Null value in the child context is lost if non-null value set in the parent | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Oleg Besedin <ob1.eclipse> | ||||
| Component: | E4 | Assignee: | Project Inbox <e4.runtime-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | ob1.eclipse, remy.suen | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Patch applied to CVS Head. |
Created attachment 170880 [details] Patch The EclipseContext has a bug in the treatment of locally set null values. If non-null value is set in a parent context, it will be returned instead. Thank you goes to Remy for noticing this!