Community
Participate
Working Groups
Bug 326602 was supposed to fix auto activation for JS in webpages. Problem is that approach used overriding methods in StructuredTextViewerConfigurationJSDT and JSDTStructuredTextViewerConfigurationJSP. The problem with doing that is that the StructuredTextViewerConfiguration extension point was not designed to have more then one StructuredTextViewerConfiguration provided for the same conetent type which is what happens when JSDT and SSE both provided a StructuredTextViewerConfiguration for the HTML and JSP content types. Because of this the JSDT specific StructuredTextViewerConfiguration do not always get used. This is dependent on load order, and while in WTP it tends to be the case that JSDT happens to load first it has been noticed in adopter products this is not always the case. The fix for this is to use a new extension point being provided by the SSE team in bug 328366. This addition to the existing completionProposal extension point will allow JSDT to provide auto activation characters to be used in its partition types without the involvement of StructuredTextViewerConfigurations.
Created attachment 182038 [details] Patch - Option 1 Patch that takes advantage of the addition to the completionProposal extension point provided by Bug 328366. This option one leaves the JSDT completionProposal extension point where it is in jsdt.web.ui but Nick pointed out that JSDT is referring to the JSP content type in that extension and that part of the extension should really be moved to our JSP plugin jsdt.web.support.jsp. Thus I will be providing a second patch that both takes advantage of the new SSE changes and moves the JSP contribution to where it "should" be.
Created attachment 182046 [details] Patch - Option 2 As described in my last comment this patch moves the JSP JSDT content assist contribution to the jsdt.web.support.jsp. Also in both patches I essentially reverted the initial change put in with Bug 326602. But moved the functionality of the existing SDTStructuredContentAssistProcessor to the new JSDTAutoActivationDelegate.
Comment on attachment 182038 [details] Patch - Option 1 We decided offline that it was a good idea to move the JSP content assist extension to the JSDT JSP plugin, thus leaving just option 2 up for review.
Created attachment 185286 [details] additional patch Didn't work until I made the attached changes.
Released. Ian, please double-check the code changes when verifying.
Why are you using the super values before the local values? What was the issue? Last I tested this it worked.
Created attachment 185308 [details] update patch Oh, i see whats going on now, because SSE isn't implementing its own new AutoActivationDelegate and overriding the parent implementation. Attaching a Patch to update JSDT to not override the functions it doesn't need to in JSDTStructuredContentAssistProcessor. And actually since there is nothing in there anymore, it may not even be needed anymore.
