[JBoss JIRA] Created: (JBIDE-2616) Invalid thread access exception is occured when set new server runtime on New Seam Project wizard.
by Anton Klimkovich (JIRA)
Invalid thread access exception is occured when set new server runtime on New Seam Project wizard.
--------------------------------------------------------------------------------------------------
Key: JBIDE-2616
URL: https://jira.jboss.org/jira/browse/JBIDE-2616
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.0.0.alpha
Environment: JBT 3.0 Alpha1. The 11 august build.
Reporter: Anton Klimkovich
EXECUTE: Open Seam perspective
EXECUTE: New -> Seam web Project
ASSERT: New Seam Project wizard is opened.
EXECUTE: Press New button for Target Runtime
EXECUTE: Select JBoss 4.2 runtime
EXECUTE: Set path to the runtime and press Finish button
FAILURE:
org.eclipse.swt.SWTException: Invalid thread access
at org.eclipse.swt.SWT.error(SWT.java:3777)
at org.eclipse.swt.SWT.error(SWT.java:3695)
at org.eclipse.swt.SWT.error(SWT.java:3666)
at org.eclipse.swt.widgets.Widget.error(Widget.java:463)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:355)
at org.eclipse.swt.widgets.Combo.addSelectionListener(Combo.java:247)
at org.eclipse.wst.common.frameworks.internal.datamodel.ui.DataModelSynchHelper.synchCombo(DataModelSynchHelper.java:496)
at org.jboss.tools.seam.ui.wizard.SeamProjectWizard.synchSeamActionModels(SeamProjectWizard.java:125)
at org.jboss.tools.seam.ui.wizard.SeamProjectWizard.access$5(SeamProjectWizard.java:107)
at org.jboss.tools.seam.ui.wizard.SeamProjectWizard$1.handleEvent(SeamProjectWizard.java:99)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.notifyListeners(FacetedProjectWorkingCopy.java:1640)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.resumeEventNotification(FacetedProjectWorkingCopy.java:1685)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.setSelectedPreset(FacetedProjectWorkingCopy.java:1054)
at org.eclipse.wst.web.ui.internal.wizards.NewProjectDataModelFacetWizard.setRuntimeAndDefaultFacets(NewProjectDataModelFacetWizard.java:261)
at org.eclipse.wst.web.ui.internal.wizards.NewProjectDataModelFacetWizard$2.propertyChanged(NewProjectDataModelFacetWizard.java:212)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.notifyListeners(DataModelImpl.java:346)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.notifyPropertyChange(DataModelImpl.java:337)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.internalSetProperty(DataModelImpl.java:183)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.setProperty(DataModelImpl.java:172)
at org.eclipse.wst.web.ui.internal.wizards.DataModelFacetCreationWizardPage$5.run(DataModelFacetCreationWizardPage.java:411)
--
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
15 years, 9 months
[JBoss JIRA] Created: (JBIDE-2620) Portlet wizards has bad label and exception for class name
by Max Rydahl Andersen (JIRA)
Portlet wizards has bad label and exception for class name
----------------------------------------------------------
Key: JBIDE-2620
URL: https://jira.jboss.org/jira/browse/JBIDE-2620
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Portal
Affects Versions: 3.0.0.alpha
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Start Seam or JSF wizard without having any portlet enabled projects
1) The label "Class name" I think should be "Superclass"
2) Clicking browser gives me a busy cursor and this in error log:
java.lang.NullPointerException
at org.jboss.tools.portlet.ui.MultiSelectFilteredFileSelectionDialog.<init>(MultiSelectFilteredFileSelectionDialog.java:143)
at org.jboss.tools.portlet.ui.internal.wizard.NewJSFPortletClassWizardPage.handleClassButtonSelected(NewJSFPortletClassWizardPage.java:131)
at org.jboss.tools.portlet.ui.internal.wizard.NewJSFPortletClassWizardPage.access$0(NewJSFPortletClassWizardPage.java:119)
at org.jboss.tools.portlet.ui.internal.wizard.NewJSFPortletClassWizardPage$1.widgetSelected(NewJSFPortletClassWizardPage.java:114)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:253)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:273)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:281)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:471)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:822)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:880)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:569)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:511)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:126)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1184)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1040)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1036)
at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1352)
at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:3894)
at org.eclipse.swt.widgets.Tree.WM_CHAR(Tree.java:5795)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3787)
at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:5791)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4528)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2370)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3420)
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:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179
--
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
15 years, 9 months
[JBoss JIRA] Created: (JBIDE-2566) Almost any editing of pages.xml throws a lot of NPE.
by Alexey Kazakov (JIRA)
Almost any editing of pages.xml throws a lot of NPE.
----------------------------------------------------
Key: JBIDE-2566
URL: https://jira.jboss.org/jira/browse/JBIDE-2566
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.0.0.alpha
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Priority: Critical
Fix For: 3.0.0.alpha
EXECUTE: Create seam project.
EXECUTE: Open pages.xml
EXECUTE: Edit <pages... -> <ages..
EXECUTE: Save the file.
There are a lot of NPE in log:
java.lang.NullPointerException
at java.lang.String.startsWith(String.java:1252)
at java.lang.String.startsWith(String.java:1281)
at org.jboss.tools.seam.ui.pages.editor.ecore.pages.impl.PagesModelImpl$ML.structureChanged(PagesModelImpl.java:332)
at org.jboss.tools.common.model.impl.XModelImpl$2.run(XModelImpl.java:493)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.jboss.tools.common.model.impl.XModelImpl.fireStructureChanged(XModelImpl.java:489)
at org.jboss.tools.common.model.impl.XModelObjectImpl.fireStructureChanged(XModelObjectImpl.java:404)
at org.jboss.tools.seam.pages.xml.model.impl.SeamPagesDiagramImpl.firePrepared(SeamPagesDiagramImpl.java:36)
at org.jboss.tools.seam.pages.xml.model.SeamPagesFileLoader.reloadProcess(SeamPagesFileLoader.java:122)
at org.jboss.tools.seam.pages.xml.model.SeamPagesFileLoader.load(SeamPagesFileLoader.java:90)
at org.jboss.tools.common.model.filesystems.impl.AbstractExtendedXMLFileImpl.loadChildren(AbstractExtendedXMLFileImpl.java:100)
at org.jboss.tools.common.model.filesystems.impl.AbstractExtendedXMLFileImpl.get(AbstractExtendedXMLFileImpl.java:47)
at org.jboss.tools.common.meta.constraint.XAdapter.getProperty(XAdapter.java:24)
at org.jboss.tools.common.model.impl.XModelObjectImpl.get_0(XModelObjectImpl.java:129)
at org.jboss.tools.common.model.impl.XModelObjectImpl.getAttributeValue(XModelObjectImpl.java:152)
at org.jboss.tools.jst.web.model.AbstractWebFileImpl.getAsText(AbstractWebFileImpl.java:50)
at org.jboss.tools.common.model.filesystems.impl.AbstractExtendedXMLFileImpl.edit(AbstractExtendedXMLFileImpl.java:153)
at org.jboss.tools.seam.pages.xml.model.SeamPagesFileLoader.update(SeamPagesFileLoader.java:133)
at org.jboss.tools.common.model.filesystems.impl.FolderImpl.reload(FolderImpl.java:539)
at org.jboss.tools.common.model.filesystems.impl.FolderImpl.updateLoaded(FolderImpl.java:471)
at org.jboss.tools.common.model.filesystems.impl.FolderImpl.update(FolderImpl.java:307)
at org.jboss.tools.common.model.filesystems.impl.FolderImpl.updateLoaded(FolderImpl.java:456)
at org.jboss.tools.common.model.filesystems.impl.FolderImpl.update(FolderImpl.java:307)
at org.jboss.tools.common.model.filesystems.impl.FolderImpl.updateLoaded(FolderImpl.java:456)
at org.jboss.tools.common.model.filesystems.impl.FolderImpl.update(FolderImpl.java:307)
at org.jboss.tools.common.model.filesystems.impl.FileSystemFolderLoader.update(FileSystemFolderLoader.java:28)
at org.jboss.tools.common.model.filesystems.impl.FileSystemsLoader.update(FileSystemsLoader.java:65)
at org.jboss.tools.common.model.filesystems.impl.FileSystemsImpl.doUpdate(FileSystemsImpl.java:279)
at org.jboss.tools.common.model.filesystems.impl.FileSystemsImpl.access$4(FileSystemsImpl.java:273)
at org.jboss.tools.common.model.filesystems.impl.FileSystemsImpl$UpdateRunnable.run(FileSystemsImpl.java:266)
at org.jboss.tools.common.model.XJob.run(XJob.java:124)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
After that pages xml editor keeps throwing NPE after every build until you restart eclipse.
--
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
15 years, 9 months
[JBoss JIRA] Created: (JBIDE-2581) VPE can't find tag library defenition of template.
by Andrei Scherbovich (JIRA)
VPE can't find tag library defenition of template.
--------------------------------------------------
Key: JBIDE-2581
URL: https://jira.jboss.org/jira/browse/JBIDE-2581
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor
Affects Versions: 3.0.0.alpha
Reporter: Andrei Scherbovich
Assignee: Maxim Areshkau
Attachments: template.jspx, testVerify.jspx
VPE can't find tag library defenition of template.
If user uses templating such as <ui:composition tamplate="..........."> then tag library defenition from template should be visible in VPE.
SEE TEST FILES ATTACHED.
In template.jspx file we have <h:outputText> component and JSF HTML tag library defenition.
In testVerify.jspx we have no JSF HTML tag library defenition, but VPE should recognize it.
--
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
15 years, 9 months