[JBoss JIRA] (JBIDE-18260) cannot open properties pages for a launch because of tern NPE'ing
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18260?page=com.atlassian.jira.plugi... ]
Victor Rubezhny reassigned JBIDE-18260:
---------------------------------------
Assignee: Victor Rubezhny
> cannot open properties pages for a launch because of tern NPE'ing
> -----------------------------------------------------------------
>
> Key: JBIDE-18260
> URL: https://issues.jboss.org/browse/JBIDE-18260
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Reporter: Max Rydahl Andersen
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.2.0.CR1
>
>
> I launch JBoss, then go under Debug to find the process to see the parameters and I get a blank page saying there are invalid values.
> In error log is this:
> java.lang.NullPointerException
> at tern.eclipse.ide.ui.properties.TernModulesPropertyPage.createContents(TernModulesPropertyPage.java:62)
> at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:233)
> at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1537)
> at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:1289)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178)
> at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1281)
> at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:699)
> at org.eclipse.jface.preference.PreferenceDialog$9$1.run(PreferenceDialog.java:730)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:725)
> at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:876)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178)
> at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:873)
> at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1708)
> at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1093)
> at org.eclipse.jface.preference.PreferenceDialog.selectSavedItem(PreferenceDialog.java:1083)
> at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.selectSavedItem(FilteredPreferenceDialog.java:757)
> at org.eclipse.jface.preference.PreferenceDialog$4.run(PreferenceDialog.java:390)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.preference.PreferenceDialog.createContents(PreferenceDialog.java:385)
> at org.eclipse.jface.window.Window.create(Window.java:435)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1101)
> at org.eclipse.ui.internal.dialogs.PropertyDialog.createDialogOn(PropertyDialog.java:83)
> at org.eclipse.ui.dialogs.PropertyDialogAction.createDialog(PropertyDialogAction.java:177)
> at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:158)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:519)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18260) cannot open properties pages for a launch because of tern NPE'ing
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-18260:
-------------------------------------------
Summary: cannot open properties pages for a launch because of tern NPE'ing
Key: JBIDE-18260
URL: https://issues.jboss.org/browse/JBIDE-18260
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml/html source editing
Reporter: Max Rydahl Andersen
Priority: Critical
Fix For: 4.2.0.CR1
I launch JBoss, then go under Debug to find the process to see the parameters and I get a blank page saying there are invalid values.
In error log is this:
java.lang.NullPointerException
at tern.eclipse.ide.ui.properties.TernModulesPropertyPage.createContents(TernModulesPropertyPage.java:62)
at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:233)
at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1537)
at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:1289)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178)
at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1281)
at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:699)
at org.eclipse.jface.preference.PreferenceDialog$9$1.run(PreferenceDialog.java:730)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:725)
at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:876)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178)
at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:873)
at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1708)
at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1093)
at org.eclipse.jface.preference.PreferenceDialog.selectSavedItem(PreferenceDialog.java:1083)
at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.selectSavedItem(FilteredPreferenceDialog.java:757)
at org.eclipse.jface.preference.PreferenceDialog$4.run(PreferenceDialog.java:390)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.preference.PreferenceDialog.createContents(PreferenceDialog.java:385)
at org.eclipse.jface.window.Window.create(Window.java:435)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1101)
at org.eclipse.ui.internal.dialogs.PropertyDialog.createDialogOn(PropertyDialog.java:83)
at org.eclipse.ui.dialogs.PropertyDialogAction.createDialog(PropertyDialogAction.java:177)
at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:158)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:519)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-16898) no error handling for nonexisting remote home
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16898?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16898:
---------------------------------------------
eh - now i'm lost....so server-config is never set even though the config property is always set as relative ?
so this is a problem for both remote and local I reckon ?
> no error handling for nonexisting remote home
> ---------------------------------------------
>
> Key: JBIDE-16898
> URL: https://issues.jboss.org/browse/JBIDE-16898
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
>
> Downloaded EAP 6.2 via downlod runtimes.
> configured it to use remote, entered in bogus name for home folder.
> This is in the console log:
> "/>
> />
> Error: Unable to access jarfile urft/jboss-modules.jar
> JBTOOLS_SERVER_START_CMD:JBoss Enterprise Application Platform 6.1+1395830330282:11785
> />"
> I would have expected some validation or better info in the console on what users should do now.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17457) JAX-RS Resource Wizard has inconsistent validation of target entity
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17457?page=com.atlassian.jira.plugi... ]
Radoslav Rábara closed JBIDE-17457.
-----------------------------------
Verified with JBDS 8.0.0.CR1-v20140831-0335-B201
> JAX-RS Resource Wizard has inconsistent validation of target entity
> -------------------------------------------------------------------
>
> Key: JBIDE-17457
> URL: https://issues.jboss.org/browse/JBIDE-17457
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: webservices
> Affects Versions: 4.2.0.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.CR1
>
>
> The wizard should let the user click on the 'Finish' button even if no 'Target entity was specified', in which case, the JAX-RS Resource Methods checkboxes should be all unselected and disabled and the generated code should only contain the package and type declaration (no method)
> BUT when you actually type in class for entity and it does not exist or you edit the field to be be blank the wizard shows an error where it should just be a warning and allow you to create it as if you hadn't edited the field.
> Should only make it an error if one of the methodstub checkboxes actually requires a type.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-16898) no error handling for nonexisting remote home
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16898?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-16898:
---------------------------------------
[~maxandersen] it is set - if I change it from standalone.xml to standalone.xml-- it is reflected in the launch command. But only the xml file is taken into account, not the dir.
> no error handling for nonexisting remote home
> ---------------------------------------------
>
> Key: JBIDE-16898
> URL: https://issues.jboss.org/browse/JBIDE-16898
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
>
> Downloaded EAP 6.2 via downlod runtimes.
> configured it to use remote, entered in bogus name for home folder.
> This is in the console log:
> "/>
> />
> Error: Unable to access jarfile urft/jboss-modules.jar
> JBTOOLS_SERVER_START_CMD:JBoss Enterprise Application Platform 6.1+1395830330282:11785
> />"
> I would have expected some validation or better info in the console on what users should do now.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18005) Disable automatic Portlet configuration via pom property
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18005?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-18005.
------------------------------------
verified in JBDS 8.0.0.CR1-v20140831-0335-B201
> Disable automatic Portlet configuration via pom property
> --------------------------------------------------------
>
> Key: JBIDE-18005
> URL: https://issues.jboss.org/browse/JBIDE-18005
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: maven
> Affects Versions: 4.2.0.Beta3
> Reporter: Fred Bricon
> Assignee: Denis Golovin
> Fix For: 4.2.0.CR1
>
>
> add support for <m2e.portlet.activation>false</m2e.portlet.activation> to prevent automatic Portlet configuration (Or force it if workspace preference has it disabled)
> an xml template should be made available for ctrl+space in the properties section. See JBIDE-17885
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months