Community
Participate
Working Groups
Created attachment 109788 [details] Log file See attached log file. I think JSDT should be more tolerant to binding resolving issues, since JavaScript is a dynamic language unlike Java.
Created attachment 110398 [details] patch
Applied the patch.
Created attachment 110905 [details] Additional fixes
Some exceptions still happen. Please see additional fixes patch.
Created attachment 111057 [details] Additional fixes
Created attachment 111059 [details] Additional fixes
The 1st patch is already checked in, so it is only the last 3 patches up for review. I will be honest and say I have not been able to reproduce this problem, but looking at the patches they do look very safe and do fix some possible exposures. Zend is an JSDT adopter and they would like to have this fixed in 3.0.2. * Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such. The javascript validation gives incorrect output when validating large javascript frameworks. * Is there a work-around? If so, why do you believe the work-around is insufficient? * How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? JSDT units tests * Give a brief technical overview. Who has reviewed this fix? I have reviewed it. * What is the risk associated with this fix? minimal risk involved. changes are mainly null pointer checks or initialization of variables so they are not null.
I'm ok with it, since request from Zend, and Phil judges it safe. Michael, any idea why Phil wouldn't be able to reproduce?
Just to record this, I tried importing dojo 1.1.1 into a new javascript project, and did not receive the exceptions. TypeBindings being null has been problem in the past, so I can believe Michael saw this under some condition.
Applied the patches.