[jbosstools-issues] [JBoss JIRA] Assigned: (JBIDE-3144) EL resolution causes VPE to loose its synchronization

[Maxim Areshkau (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBIDE-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxim Areshkau reassigned JBIDE-3144:
-------------------------------------

    Assignee: Maxim Areshkau


> EL resolution causes VPE to loose its synchronization
> -----------------------------------------------------
>
>                 Key: JBIDE-3144
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3144
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Visual Page Editor core
>    Affects Versions: 3.0.0.beta1
>            Reporter: Max Rydahl Andersen
>            Assignee: Maxim Areshkau
>            Priority: Blocker
>             Fix For: 3.0.0.cr1
>
>
> (I've only tried this with the Seam generated projects, but I don't think it is specific to it)
> EXECUTE: Create a Seam web project
> EXECUTE: Change template="layout/template.xhtml" to template="#{request.contextPath}/layout/template.xhtml">
> EXECUTE: Setup request.contextPath = ./ in page design options
> EXECUTE: Refresh editor
> ASSERT: Editing continues to work
> ACTUAL: Edits is not visible in VPE and edits through VPE result in edits in the top line of the file instead of inside the file.
> This is marked blocker since EL resolution is rather pointless if it breaks up the editor ;(
> Sometime I got this exception:
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
> at org.eclipse.swt.SWT.error(SWT.java:3777)
> at org.eclipse.swt.SWT.error(SWT.java:3695)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3800)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> 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.equinox.launcher.Main.invokeFramework(Main.java:549)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.cleanHead(VpeVisualDomBuilder.java:1507)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.rebuildDom(VpeVisualDomBuilder.java:241)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.updateNode(VpeVisualDomBuilder.java:944)
> at org.jboss.tools.vpe.editor.VpeController.notifyChangedInUiThread(VpeController.java:670)
> at org.jboss.tools.vpe.editor.VpeController$1.runInUIThread(VpeController.java:525)
> at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133)
> ... 22 more

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira