Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 355903 - Records contain eze$$isNull which is not supported in EDT
Summary: Records contain eze$$isNull which is not supported in EDT
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P1 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-25 20:09 EDT by Joseph Vincens CLA
Modified: 2017-02-23 14:16 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joseph Vincens CLA 2011-08-25 20:09:30 EDT
If it is decided to leave this the clone method must be fixed.
Copy the records HttpREST, HttpRequest, HttpResponse from the system parts
eglx.http and generate them to JS. In HttpREST th eeze$$Clone method is not
correct.
Record field should be cloned not copied:
	ezert$$2.setNull(ezert$$1eze$$isNull);
Should be generated as:
	ezert$$2.setNull(ezert$$1.eze$$isNull);
A . is missing from the RHS of the setNull.
Comment 1 Scott Greer CLA 2011-10-19 23:05:57 EDT
After talking to Matt and Joe, we concluded that EDT would not use RBD's convention for marking things like records as null with a flag named eze$$isNull on the correspondsing JS object;  instead, EDT's runtime will simply use JavaScript null.  

The EDT runtime no longer contains any references to this flag, and I could find only a handful of references in JS gen which were all commented out -- I'm removing them just to clean up the source.
Comment 2 Joseph Vincens CLA 2011-10-24 16:13:52 EDT
verified