Community
Participate
Working Groups
If a user attempts to open any source editor (HTML, XML, CSS) without the JSP plugins loaded then the source editor will open but have an error message saying: Could not open the editor: An unexpected exception was thrown. java.lang.NullPointerException at org.eclipse.wst.sse.ui.StructuredTextEditor.calculatePriority(Unknown Source) at org.eclipse.wst.sse.ui.StructuredTextEditor.installCharacterPairing(Unknown Source) at org.eclipse.wst.sse.ui.StructuredTextEditor.createPartControl(Unknown Source) ...
Created attachment 175725 [details] patch against 3.2.1
Simple fix for a severe problem.
I was hit by this after the upgrade of WTP to 3.2.1. Had to revert back to 3.2.0 to be able to open HTML, XML, XSL and PHP files.
What fix caused this regression? I guess you know this, but will say it anyway ... I think this would emphasize the need a little better testing of "reduced" installs? We may also want to consider running "xml, html, and css unit tests' in a "reduced" install during the junit tests. That'd be a lot of work, but might help avoid this kind of problem in future. (Ironic ... I remember when a main reason we'd do smoke testing in 'source editing' was just to make sure the editors all opened ... there were so many cases where unit tests would pass but editors wouldn't open, or you couldn't type, or something ... years and years ago). Litrik, what do you install exactly that you ran into this problem? Just roll your own? Or is there some wide-spread distribution that surfaces this problem?
(In reply to comment #4) > Litrik, what do you install exactly that you ran into this problem? Just roll > your own? Or is there some wide-spread distribution that surfaces this problem? I started with a clean install of Eclipse 3.6 Classic and added some parts of WTP. I don't use JSP at all so I install only those parts of WTP that will give me XML, HTML, CSS and JavaScript editors. Currently I have installed the following features: Eclipse Faceted Project Framework Version: 3.2.1.v201007151559-377A88s73533F5H384A JavaScript Development Tools Version: 1.2.0.v201005270528-7C78FGDF9JgLWLMBWz-Ose6 Eclipse Web Developer Tools Version: 3.2.0.v201005241510-7O7CFb3EMf84nP-FHuc10NTz--M3 Eclipse XML Editors and Tools Version: 3.2.0.v201005241510-7H7AFUIDxumQGOb7ocjUR2Pvz-28 Eclipse XSL Developer Tools Version: 1.1.3.v201006151143-67K0BgJ9DIATEXATHP Eclipse XSL Developer Tools Version: 1.1.0.v201005241600-7S7WFAKFIpS---NRIS1pbfYBUIQ
(In reply to comment #4) > What fix caused this regression? It was triggered by the changes for bug 276702 referring to a content type in a plug-in not included by that plug-ins required features, but the flaw was introduced as part of the fix for bug 294088.
Released to 3.2.2.
Is there anyway this could get pushed out before SR1? The standard 3.6 JavaScript build exhibits this problem after updating a feature that depends upon JSDT. We have the following plugin dependencies: org.eclipse.wst.jsdt.core org.eclipse.wst.jsdt.ui org.eclipse.wst.sse.core org.eclipse.wst.html.core org.eclipse.wst.sse.ui org.eclipse.wst.jsdt.debug.core org.eclipse.wst.jsdt.debug.ui org.eclipse.wst.xml.ui To reproduce: 1. Download and install eclipse-javascript-helios-win32-x86_64.zip 2. Create a Static Web Project, add index.html 3. Add our feature that has the dependencies above, and don't un-check "Contact all update sites during install..." 4. Restart as directed Editing html is now broken.
(In reply to comment #8) > Is there anyway this could get pushed out before SR1? Installing the JST Web feature also gets around the problem.
