Community
Participate
Working Groups
In org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor, the methods beginProcessing and endProcessing both call getValidatorStrategy without checking for null on the return even though the method can return null. This can (and does) lead to the dreaded "Processing Dirty Region" exploding dialog and error log message. It also results in region dependent services in the effected StructuredTextEditor (in my case JSP editor) to throw their own nasty and often uncaught exceptions and any event cripples the editor in these dependent areas. Problem has been noted in several recent builds including WTP 1.5M5.
Fixed. Thanks for the keen eye, Cameron.
The problem seems to be a symptom of a deeper problem related to why getValidationStrategy returns null. It seems that the system can get into a state where the IDocument attached to the StructuredTextViewer does not match the IDocument registered with with StructuredModelManager. This causes the system to be unable to resolve the content type of the IDocument even though all the information is there. This problem is far more serious because not even deleting the underlying IResource (in my case a JSP) seems to correct the problem. I am still characterizing and will open another bug once I have found the root of the problem.
I'd like to nominate this one as a "greatbug", since at least one "special case" was discovered by Cameron in his JSF, and he dug right in and found the problem in our code. This was especially important in this case, since this one tiny bug (of not handling 'null' correctly, would "cascade" up the change of dependent components resulting in some bad overall IDE failure (not just a log message). Much thanks Cameron.
Verify fixed in 1.5RC4.
Closing
