[ratewatch]

I did an install of 5.1 this morning (not the upgrade) and am now receiving this error when trying to edit JSP pages:

org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.SWT.error(SWT.java:3374)
at org.eclipse.swt.SWT.error(SWT.java:3297)
at org.eclipse.swt.SWT.error(SWT.java:3268)
at org.eclipse.swt.widgets.Widget.error(Widget.java:435)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:330)
at org.eclipse.swt.widgets.Control.setLayoutData(Control.java:2386)
at com.genuitec.eclipse.webdesigner3.design.DesignEditSystem.createDesignView(DesignEditSystem.java:73)
at com.genuitec.eclipse.webdesigner3.WebDesigner3.createDesignView(WebDesigner3.java:74)
at com.genuitec.eclipse.webdesigner3.editors.WebDesignerMultiPageEditor.createDesignView(WebDesignerMultiPageEditor.java:399)
at com.genuitec.eclipse.webdesigner3.editors.WebDesignerMultiPageEditor.createDesignPage(WebDesignerMultiPageEditor.java:371)
at com.genuitec.eclipse.webdesigner3.editors.WebDesignerMultiPageEditor.createPages(WebDesignerMultiPageEditor.java:293)
at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:276)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:596)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566)
at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:214)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2595)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2528)
at org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPage.java:2520)
at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2505)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2500)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2485)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:388)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:350)
at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:275)
at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:139)
at org.eclipse.jdt.internal.ui.actions.OpenActionUtil.open(OpenActionUtil.java:49)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:190)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:174)
at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:267)
at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:243)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen(PackageExplorerActionGroup.java:306)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$4.open(PackageExplorerPart.java:653)
at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:817)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.runtime.Platform.run(Platform.java:843)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:149)
at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:815)
at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1069)
at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1168)
at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:249)
at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:243)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:283)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
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.invokeFramework(Main.java:336)
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)

I already tried to startup MyEclipse with the -clean flag to no avail.

Also, on another note, I thought 5.1 was supposed to fix the “cannot be resolved” warnings?

[ratewatch]

Update: I resolved the JSP editor issue. I uninstalled both 5.01 and 5.1 and installed only 5.1 again, and problem solved. They obviously don’t play nice together, but I guess that makes sense.

But, I’m still curious as to the “cannot be resolved” errors (ie using var in datatable). They are really cluttering up the Problems tab (currently about 220 warnings due to this).

[Riyad Kalla]

ratewatch,
Sorry for the headache with the update. Glad it’s working though (thank you for following up).

Now as for the cannot be resolved errors… are these for JSP pages? Can you give code snippets of examples?

[warrenthebrown]

I had the same problem. Sure would be nice if there were some warning about the need to uninstall 5.0.1 first.

[Riyad Kalla]

Warren,
It should actually be disabled (Help > Software Updates > manage Configuration > Right click on 5.0.1, Disable, and restart)

We tried this internally. I’m not sure why it’s not properly disabling the previous install like it should be.

[ratewatch]

Here is a very simple page that shows the problem:

<f:view xmlns:f="http://java.sun.com/jsf/core"
        xmlns:t="http://myfaces.apache.org/tomahawk"
        xmlns:jsp="http://java.sun.com/JSP/Page"
        xmlns:h="http://java.sun.com/jsf/html">
<html>
<head>

    <script language="javascript" src="/BankingMyWay/js/disableSearchSubmit.js" />

    <f:loadBundle var="bundle" basename="com.bankingmyway.resourcebundles.Subscription" />
    <f:loadBundle var="commonBundle" basename="com.bankingmyway.resourcebundles.Common" />
    <f:loadBundle var="statusBundle" basename="com.bankingmyway.resourcebundles.ConnectionStatus" />

    <title><h:outputText value="#{bundle.subscriptionHomeTitle}" /></title>
    
    <t:stylesheet path="#{commonBundle.cssPath}" />
    <t:stylesheet path="#{statusBundle.cssPath}" />
    
</head>
<body>
    <h:form id="criteriaForm">
        <h:panelGrid columns="1">
        <h:panelGroup styleClass="pageWrapper">
        
            <h:panelGroup styleClass="header">
                <h:commandLink action="linkToHome">
                    <h:graphicImage id="stdHeader"  styleClass="noImageBorder" url="/images/content/header.jpg" />
                </h:commandLink>
            </h:panelGroup>
            
            <h:panelGroup styleClass="sideAd">
                <h:outputText styleClass="centered" value="Ads" />
            </h:panelGroup>
             
            <h:outputText value="Yay! Pay us money!" />
             
            <h:panelGroup styleClass="footer">
                <h:panelGroup styleClass="centered">
                        <h:outputText value="Footer" />
                </h:panelGroup>
            </h:panelGroup>
    
        </h:panelGroup>
        </h:panelGrid>
    </h:form>
    
</body>
</html>
</f:view>

When I mouse over the yellow-underlined warnings, I get “Undefined attribute name ‘var'” for all attributes (the name changes of course) and “bundle cannot be resolved” for all places I’m using the bundle name. The page works just fine, no problems there, just the annoying 200 warnings in our project makes it difficult to find the meaningful ones.

Thanks for looking further into this, we appreciate it.

[Riyad Kalla]

ratewatch,
I’ll be the first to admit that I don’t know everything about the JSP 2.0/JSP Document specification, but using a template for a JSP Document with JSF tags as such:

<?xml version="1.0" encoding="UTF-8"?>

<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.0"
    xmlns:f="http://java.sun.com/jsf/core"
    xmlns:h="http://java.sun.com/jsf/html">
    <jsp:directive.page contentType="text/html; charset=UTF-8" />
    <jsp:text>
        <![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> ]]>
    </jsp:text>
    <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
        <head>
            <title>My JSP 'MyJsp.jsp' starting page</title>
            <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
            <meta http-equiv="keywords" content="keyword1,keyword2,keyword3" />
            <meta http-equiv="description" content="This is my page" />
            <!--
                <link rel="stylesheet" type="text/css" href="styles.css" />
            -->
        </head>
        <body>
            This is my JSF page. <br />
        </body>
    </html>
</jsp:root>

I was able to get rid of all the unknown tag warnings in the page… I think your page definition may be incorrect, or a non-standard format that some implementations honor, but others don’t? I’m not sure. I know that if you define the taglibs in the root element as I have above, you can use them correctly with no error markers.

[ratewatch]

Thanks for the reply. The page definition modification has solved many of the ‘cannot be resolved’ warnings.

Still have a couple though…

<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.0"
           xmlns:f="http://java.sun.com/jsf/core"
           xmlns:h="http://java.sun.com/jsf/html"
           xmlns:ice="http://www.icesoft.com/icefaces/component"
           xmlns:t="http://myfaces.apache.org/tomahawk">

The ‘jsp’ one has no warning but the other four(4) do. ‘ Undefined attribute name (xmlns:f) ‘

Also, have a warning ‘cannot be resolved’ with curQuestion in the following snippet:

 
     <ice:dataTable var="curQuestion" value="#{LostPasswordBean.criteria.questions}" styleClass="innerLoginGrid">
        <ice:column>
        <ice:outputText value="#{curQuestion.question}" /> // warning on this line 
        <ice:inputText value="#{LostPasswordBean.criteria.answers[curQuestion.id]}" />
            <f:verbatim><br /></f:verbatim>
        </ice:column>
    </ice:dataTable>

Pages all still work fine, just would be nice to clear up these warnings so that when something actually needs to be fixed, it can be found.
Thanks for your help.

[Riyad Kalla]

The JSF issues may be a result of having the wrong version of JSF libraries in your path. For example, expand the JSF JAR files, look in the META-INF dir for the TLDs, and then open one, check about 5 tags down for the <uri> tag, this gives the default URI. Does it match what you have in the page?

[Author]

Posts