[JBoss JIRA] (JBIDE-11703) NPE in CDI ClassPathMonitor
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-11703:
-----------------------------------
Summary: NPE in CDI ClassPathMonitor
Key: JBIDE-11703
URL: https://issues.jboss.org/browse/JBIDE-11703
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Affects Versions: 3.3.0.Beta3
Reporter: Fred Bricon
Assignee: Alexey Kazakov
Fix For: 3.3.0.Beta3
Will importing a HTML5 project from Openshift, I got that NPE :
{noformat}
org.jboss.tools.common.validation.JBTValidationException
at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:101)
at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.NullPointerException
at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.init(ClassPathMonitor.java:53)
at org.jboss.tools.cdi.core.CDICoreNature.setProject(CDICoreNature.java:111)
at org.eclipse.core.internal.resources.NatureManager.createNature(NatureManager.java:234)
at org.eclipse.core.internal.resources.Project.getNature(Project.java:448)
at org.jboss.tools.cdi.core.CDICorePlugin.getCDINature(CDICorePlugin.java:137)
at org.jboss.tools.cdi.core.CDICorePlugin.getCDI(CDICorePlugin.java:145)
at org.jboss.tools.cdi.internal.core.validation.CDIProjectTree.addProject(CDIProjectTree.java:56)
at org.jboss.tools.cdi.internal.core.validation.CDIProjectTree.<init>(CDIProjectTree.java:44)
at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.getProjectTree(CDICoreValidator.java:226)
at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.getValidatingProjects(CDICoreValidator.java:221)
at org.jboss.tools.common.validation.ValidationContext.init(ValidationContext.java:97)
at org.jboss.tools.common.validation.ValidationContext.<init>(ValidationContext.java:43)
at org.jboss.tools.common.validation.ContextValidationHelper.getValidationContextManager(ContextValidationHelper.java:162)
at org.jboss.tools.common.validation.ContextValidationHelper.getValidationContextManager(ContextValidationHelper.java:154)
at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:65)
... 2 more
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (JBIDE-4523) Visual Page Editor doesn't work with Eclipse 3.5 OSX Cocoa
by Cesar Perez (JIRA)
Visual Page Editor doesn't work with Eclipse 3.5 OSX Cocoa
----------------------------------------------------------
Key: JBIDE-4523
URL: https://jira.jboss.org/jira/browse/JBIDE-4523
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.1.0.M1
Environment: Mac OSX 10.5.7, Eclipse 3.5 JEE Cocoa, JBoss Tools 3.1.0.M1
Reporter: Cesar Perez
The Visual Page Editor does not work under the final version of Eclipse 3.5 JEE Cocoa for Mac OSX and JBoss Tools 3.1.0.M1, the error is due to a missing cocoa version of XUL runner as you can see in the following stacktrace:
org.jboss.tools.vpe.xulrunner.XulRunnerException: Bundle org.mozilla.xulrunner.cocoa.macosx is not found.
at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.getXulRunnerPath(XulRunnerBrowser.java:219)
at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.initXulRunner(XulRunnerBrowser.java:114)
at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:85)
at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:135)
at org.jboss.tools.vpe.editor.mozilla.MozillaPreview$1.<init>(MozillaPreview.java:59)
at org.jboss.tools.vpe.editor.mozilla.MozillaPreview.createPartControl(MozillaPreview.java:59)
at org.jboss.tools.vpe.editor.VpeEditorPart.createPreviewBrowser(VpeEditorPart.java:921)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:248)
at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart$2.widgetSelected(JSPMultiPageEditorPart.java:106)
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.Display.sendEvent(Display.java:3542)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1247)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1270)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1255)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1076)
at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3256)
at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:2045)
at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:323)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3542)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1247)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1270)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1255)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1076)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3440)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3099)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
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:194)
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:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
--
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
13 years, 7 months
[JBoss JIRA] Created: (JBIDE-3708) Add possibilities of components' rendering inside body of some ajax tags.
by Yura Zhishko (JIRA)
Add possibilities of components' rendering inside body of some ajax tags.
-------------------------------------------------------------------------
Key: JBIDE-3708
URL: https://jira.jboss.org/jira/browse/JBIDE-3708
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Visual Page Editor Templates
Affects Versions: 3.0.0.CR2
Reporter: Yura Zhishko
Assignee: Maxim Areshkau
1) Import attached project into workspace
2) Run it on server
ASSERT: Some of these components do not have visual representation, but body content is rendered OK. On pages you will find comments with a real behavior of components (in all components, not marked as "Here is OK", components of a body are rendered at first by turn and then component is rendered itself and appears if it has visual representation).
Also pay attention to components marked as jira's issues.
P. S. This is not a full list of components, others components will be tested soon.
--
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
13 years, 7 months