[Ralf Edmund Stranzenbach]

While rebuilding my project on 3.8.2GA i get the following exceptions:

java.lang.NullPointerException
    at com.ibm.sse.model.html.text.rules.StructuredTextPartitionerForHTML.createPartition(Unknown Source)
    at com.ibm.sse.model.jsp.text.rules.StructuredTextPartitionerForJSP.setInternalPartition(Unknown Source)
    at com.ibm.sse.model.text.rules.StructuredTextPartitioner.internalGetPartition(Unknown Source)
    at com.ibm.sse.model.text.rules.StructuredTextPartitioner.getPartition(Unknown Source)
    at com.ibm.sse.model.text.rules.StructuredTextPartitioner.getContentType(Unknown Source)
    at com.ibm.sse.model.internal.text.BasicStructuredDocument.getContentType(Unknown Source)
    at org.eclipse.jface.text.TextUtilities.getContentType(TextUtilities.java:368)
    at org.eclipse.jface.text.contentassist.ContentAssistant.getProcessor(ContentAssistant.java:1392)
    at org.eclipse.jface.text.contentassist.ContentAssistant.getCompletionProposalAutoActivationCharacters(ContentAssistant.java:1625)
    at org.eclipse.jface.text.contentassist.ContentAssistSubjectControlAdapter.getCompletionProposalAutoActivationCharacters(ContentAssistSubjectControlAdapter.java:279)
    at org.eclipse.jface.text.contentassist.ContentAssistant$AutoAssistListener.keyPressed(ContentAssistant.java:284)
    at org.eclipse.jface.text.contentassist.ContentAssistant$AutoAssistListener.verifyKey(ContentAssistant.java:309)
    at org.eclipse.jface.text.TextViewer$VerifyKeyListenersManager.verifyKey(TextViewer.java:403)
    at org.eclipse.swt.custom.StyledTextListener.handleEvent(StyledTextListener.java:55)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:820)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:805)
    at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:613)
    at org.eclipse.swt.custom.StyledText.handleKeyDown(StyledText.java:5000)
    at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:4747)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:820)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:805)
    at org.eclipse.swt.widgets.Control.sendKeyEvent(Control.java:1734)
    at org.eclipse.swt.widgets.Control.sendKeyEvent(Control.java:1730)
    at org.eclipse.swt.widgets.Control.WM_KEYDOWN(Control.java:3517)
    at org.eclipse.swt.widgets.Control.windowProc(Control.java:2997)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:3338)
    at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
    at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1473)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2429)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1377)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:254)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
    at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:96)
    at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:335)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:183)
    at org.eclipse.core.launcher.Main.run(Main.java:644)
    at org.eclipse.core.launcher.Main.main(Main.java:628)

Unhandled event loop exception
An exception stack trace could not be found.
eclipse.buildId=I200406251208
java.version=1.5.0
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE

After all the JSPs are not completely checked and the overall performance is very poor.

The project is based on Servlet-API 2.4 and JSP 2.0 using the Expression Library and custom tag libraries.

[Riyad Kalla]

Are you able to use the -vm argument when you launch Eclipse to specify a 1.4.2 JDK instead of Java 5.0? Neither Eclipse or MyEclipse are certified to run on a 1.5 VM (yet).

[Ralf Edmund Stranzenbach]

@support-rkalla wrote:

Are you able to use the -vm argument when you launch Eclipse to specify a 1.4.2 JDK instead of Java 5.0? Neither Eclipse or MyEclipse are certified to run on a 1.5 VM (yet).

Thank you for this hint. This removes the annoying Exceptions. But there still is the behaviour with validation errors on jsp pages:

<a href="actor_deactivate.do?actorId=${row.actorId}">löschen</a>

This line results in a “No start Tag (<a>)” error with incomplete syntax highlighting on the jsp page.

[Riyad Kalla]

Ahh, you can turn off HTML validation for your project by going to project properties > MyEclipse-Validation > uncheck HTML Validation.

The HTML validation is strict HTML 4.01, and there are things that almost no one does that it will complain about, so most people like to turn it off 😉

[Ralf Edmund Stranzenbach]

Hmm, after disabling the html validation the error messages are gone. But after all i’ve observed that the outline view still shows up with a syntax-tree that does not match the actual files content. After just putting in a single blank, the syntax highlighting works as expected and the outline contains the documents structure.

BTW. The HTML and BODY element is missing in my jsp fragment but it shoul be more ore less correct html.

[Scott Anderson]

Ralf,

The issue here is that the incompleteness of the JSP combined with the formatting / complexity of the JSP is causing a problem for
the JSP parser. That’s why adding the blank fixed the highlighting; it made the page something understandable again. We’ve
seen this behavior with only a few JSP pages, but are aware of the issue and will be working to enahance the parser in
subsequent releases so this problem appears less often. Of course, this is no easy task given that JSP pages aren’t exactly
a well-formed grammar, being a hodge-podge of HTML, XML, Java, and custom tags.

[Author]

Posts