[JBoss JIRA] (JBIDE-11846) NPE when creating runtime
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-11846:
--------------------------------------
Summary: NPE when creating runtime
Key: JBIDE-11846
URL: https://issues.jboss.org/browse/JBIDE-11846
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Reporter: Alexey Kazakov
Assignee: Rob Stryker
I got this NPE when was trying to create an AS 7.1 runtime (with Server).
{code}
java.lang.NullPointerException
at org.jboss.ide.eclipse.as.core.resolvers.ConfigNameResolver.findJBossServerRuntime(ConfigNameResolver.java:146)
at org.jboss.ide.eclipse.as.core.resolvers.ConfigNameResolver.handleAS7ConfigFile(ConfigNameResolver.java:129)
at org.jboss.ide.eclipse.as.core.resolvers.ConfigNameResolver.resolveValue(ConfigNameResolver.java:101)
at org.eclipse.core.internal.variables.DynamicVariable.getValue(DynamicVariable.java:54)
at org.eclipse.core.internal.variables.StringSubstitutionEngine.resolve(StringSubstitutionEngine.java:267)
at org.eclipse.core.internal.variables.StringSubstitutionEngine.substitute(StringSubstitutionEngine.java:192)
at org.eclipse.core.internal.variables.StringSubstitutionEngine.performStringSubstitution(StringSubstitutionEngine.java:86)
at org.jboss.ide.eclipse.as.core.resolvers.ConfigNameResolver.performSubstitutions(ConfigNameResolver.java:64)
at org.jboss.ide.eclipse.as.core.resolvers.ConfigNameResolver.performSubstitutions(ConfigNameResolver.java:52)
at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.setEffectiveFilePattern(XPathQuery.java:117)
at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathQuery.<init>(XPathQuery.java:98)
at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel.addQueriesToCategoryFromDefaultFile(XPathModel.java:332)
at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel.loadDefaultPortQueries(XPathModel.java:306)
at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel.handleAddJBossXPaths(XPathModel.java:96)
at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel.access$1(XPathModel.java:95)
at org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel$1.run(XPathModel.java:82)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
I tried a few times but got this NPE just once.
--
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, 10 months
[JBoss JIRA] (JBIDE-11920) NewProjectExamplesReadyPage should wait for running jobs
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-11920:
----------------------------------
Summary: NewProjectExamplesReadyPage should wait for running jobs
Key: JBIDE-11920
URL: https://issues.jboss.org/browse/JBIDE-11920
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central, project-examples
Affects Versions: 3.3.0.Beta3
Environment: JBT 3.3.0.Beta3b
EAP 6.0 ER5, EAP6 ER6.1 mvn repo
Reporter: Radim Hopp
Assignee: Snjezana Peco
Fix For: 3.3.0.CR1
Attachments: JavaEEWebapp1.png, JavaEEWebapp2.png, JavaEEWebapp4.png
When creating Java EE Web Project from central with EAP 6 ER6.1 maven repository and clean local maven repository, NewProjectExamplesReadyPage shows checked "Show Quick Fix dialog" even though there is no error in currently imported project/example.
I think this happens because NewProjectExamplesReadyPage doesn't wait for running jobs (especifically JBoss Tools Project Validator). Because when th Ready Page pops up, JBT Project validator is still running and there is an error until it finishes.
Hope it will be more clear from screenshots
--
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, 10 months
[JBoss JIRA] (JBIDE-11792) Incomplete deploy after undeploying and deleting a current deploy
by Lukas Kalinski (JIRA)
Lukas Kalinski created JBIDE-11792:
--------------------------------------
Summary: Incomplete deploy after undeploying and deleting a current deploy
Key: JBIDE-11792
URL: https://issues.jboss.org/browse/JBIDE-11792
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers, maven
Affects Versions: 3.2.2.Final
Environment: Eclipse 3.7.2 @ Mac OSX 10.7.3 (Lion), MacBook Air
Reporter: Lukas Kalinski
Assignee: Rob Stryker
As I don't have time to reformulate myself, I just post what I've written on the forum earlier:
I recently installed Eclipse 3.7.2 on Mac OSX 10.7.3 (Lion), together with the latest JBoss Tools package. As I am new to JBoss Tools (and Apache Maven that it's using in my projects) I decided to get familiar with it before going on with something serious. So I created a new JBoss Central/Spring MVC Project. After that I added a server instance (JBoss AS 7.1.1) inside Eclipse, and deployed this unmodified project template using the Project/Run As/Run on server way. This works perfectly! However, if I for some reason decide that I would like to undeploy the project, and then deploy it again (i.e. undeploy using JBoss Management, then delete the exploded war-dirs, restart the server, and finally deploy as described above), I end up with everything being deployed, EXCEPT for everything that is in the webapp directory (the one that's created by default in this project template). As a consequence, the web application won't run anymore.
Now this is what I've tried without any success:
- Restart Eclipse;
- Delete every possible file in the JBoss AS directory, that could have something cached inside it;
- Committed the whole project tree into GIT, in order to check whether Eclipse changes some config setting (it doesn't);
- Various combinations of the above, together with a lot of other not-remembered steps ...
I could add to this that what "solves" the problem is to refactor the project name to a new one; eg, if your project is called test, then refactor it to test2 and the problem is solved. When going back to the old name ("test" in the mentioned example), the problem will still be gone. This is not a nice solution however (especially if you have your project in git/svn etc) ... and the fact that it works makes the whole problem even more weird.
--
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, 10 months
[JBoss JIRA] (JBIDE-12039) ClassCastException when loading gears in new app wizard
by Lucia Jelinkova (JIRA)
Lucia Jelinkova created JBIDE-12039:
---------------------------------------
Summary: ClassCastException when loading gears in new app wizard
Key: JBIDE-12039
URL: https://issues.jboss.org/browse/JBIDE-12039
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.CR1
Reporter: Lucia Jelinkova
Assignee: Andre Dietisheim
Fix For: 3.3.0.CR1
When I choose an existing application in new app wizard, press Back button and then Next button, I get the following error in error log:
{code}
Unhandled exception: com.openshift.internal.client.GearProfile cannot be cast to java.lang.String
java.lang.ClassCastException: com.openshift.internal.client.GearProfile cannot be cast to java.lang.String
at org.eclipse.jface.internal.databinding.swt.ComboItemsProperty$1.handleReplace(ComboItemsProperty.java:57)
at org.eclipse.core.databinding.observable.list.ListDiff.accept(ListDiff.java:123)
at org.eclipse.jface.internal.databinding.swt.ComboItemsProperty.doUpdateStringList(ComboItemsProperty.java:26)
at org.eclipse.jface.internal.databinding.swt.ControlStringListProperty.doUpdateList(ControlStringListProperty.java:38)
at org.eclipse.core.databinding.property.list.ListProperty.updateList(ListProperty.java:105)
at org.eclipse.core.internal.databinding.property.list.SimplePropertyObservableList.updateList(SimplePropertyObservableList.java:176)
at org.eclipse.core.internal.databinding.property.list.SimplePropertyObservableList.set(SimplePropertyObservableList.java:428)
at org.eclipse.core.databinding.observable.list.DecoratingObservableList.set(DecoratingObservableList.java:192)
at org.eclipse.core.databinding.UpdateListStrategy.doReplace(UpdateListStrategy.java:304)
at org.eclipse.core.databinding.ListBinding$6.handleReplace(ListBinding.java:205)
at org.eclipse.core.databinding.observable.list.ListDiff.accept(ListDiff.java:123)
at org.eclipse.core.databinding.ListBinding$5.run(ListBinding.java:165)
at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:148)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:152)
at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:170)
at org.eclipse.core.databinding.ListBinding.doUpdate(ListBinding.java:152)
at org.eclipse.core.databinding.ListBinding.access$2(ListBinding.java:145)
at org.eclipse.core.databinding.ListBinding$2.handleListChange(ListBinding.java:55)
at org.eclipse.core.databinding.observable.list.ListChangeEvent.dispatch(ListChangeEvent.java:61)
at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
at org.eclipse.core.databinding.observable.list.DecoratingObservableList.fireListChange(DecoratingObservableList.java:59)
at org.eclipse.core.databinding.observable.list.DecoratingObservableList.handleListChange(DecoratingObservableList.java:97)
at org.eclipse.core.databinding.observable.list.DecoratingObservableList$1.handleListChange(DecoratingObservableList.java:71)
at org.eclipse.core.databinding.observable.list.ListChangeEvent.dispatch(ListChangeEvent.java:61)
at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
at org.eclipse.core.databinding.observable.list.DecoratingObservableList.fireListChange(DecoratingObservableList.java:59)
at org.eclipse.core.databinding.observable.list.DecoratingObservableList.handleListChange(DecoratingObservableList.java:97)
at org.eclipse.core.databinding.observable.list.DecoratingObservableList$1.handleListChange(DecoratingObservableList.java:71)
at org.eclipse.core.databinding.observable.list.ListChangeEvent.dispatch(ListChangeEvent.java:61)
at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
at org.eclipse.core.databinding.observable.ChangeSupport.fireEvent(ChangeSupport.java:39)
at org.eclipse.core.databinding.observable.list.AbstractObservableList.fireListChange(AbstractObservableList.java:114)
at org.eclipse.core.internal.databinding.property.list.SimplePropertyObservableList.notifyIfChanged(SimplePropertyObservableList.java:567)
at org.eclipse.core.internal.databinding.property.list.SimplePropertyObservableList.access$3(SimplePropertyObservableList.java:559)
at org.eclipse.core.internal.databinding.property.list.SimplePropertyObservableList$2.run(SimplePropertyObservableList.java:78)
at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:148)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:152)
at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:170)
at org.eclipse.core.internal.databinding.property.list.SimplePropertyObservableList$1.handleEvent(SimplePropertyObservableList.java:74)
at org.eclipse.core.databinding.property.NativePropertyListener.fireChange(NativePropertyListener.java:63)
at org.eclipse.core.internal.databinding.beans.BeanPropertyListener.propertyChange(BeanPropertyListener.java:49)
at java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:335)
at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:328)
at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:263)
at org.jboss.tools.common.databinding.ObservablePojo.firePropertyChange(ObservablePojo.java:29)
at org.jboss.tools.common.ui.databinding.ObservableUIPojo.access$0(ObservableUIPojo.java:1)
at org.jboss.tools.common.ui.databinding.ObservableUIPojo$1.run(ObservableUIPojo.java:27)
at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:164)
at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:158)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:173)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:388)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1029)
at org.jboss.tools.common.ui.WizardUtils.runInWizard(WizardUtils.java:122)
at org.jboss.tools.common.ui.WizardUtils.runInWizard(WizardUtils.java:86)
at org.jboss.tools.common.ui.WizardUtils.runInWizard(WizardUtils.java:207)
at org.jboss.tools.common.ui.WizardUtils.runInWizard(WizardUtils.java:202)
at org.jboss.tools.openshift.express.internal.ui.wizard.ApplicationConfigurationWizardPage.loadOpenshiftResources(ApplicationConfigurationWizardPage.java:749)
at org.jboss.tools.openshift.express.internal.ui.wizard.ApplicationConfigurationWizardPage$9$1.run(ApplicationConfigurationWizardPage.java:655)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at org.jboss.tools.central.editors.GettingStartedPage$9.linkActivated(GettingStartedPage.java:618)
at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:199)
at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
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:344)
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:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
{code}
--
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, 10 months
[JBoss JIRA] (JBIDE-11735) NPE after importing openshift app via New Server wizard
by Stefan Bunciak (JIRA)
Stefan Bunciak created JBIDE-11735:
--------------------------------------
Summary: NPE after importing openshift app via New Server wizard
Key: JBIDE-11735
URL: https://issues.jboss.org/browse/JBIDE-11735
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers, openshift
Affects Versions: 3.3.0.Beta3
Reporter: Stefan Bunciak
Assignee: Rob Stryker
Fix For: 3.3.0.CR1
{code}
java.lang.NullPointerException
at org.eclipse.wst.common.componentcore.internal.operation.ServerContextRootUpdateOperation.execute(ServerContextRootUpdateOperation.java:40)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl$1.run(DataModelPausibleOperationImpl.java:385)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:410)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:360)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.doExecute(DataModelPausibleOperationImpl.java:247)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.executeImpl(DataModelPausibleOperationImpl.java:219)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.cacheThreadAndContinue(DataModelPausibleOperationImpl.java:89)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.execute(DataModelPausibleOperationImpl.java:207)
at org.eclipse.wst.common.componentcore.internal.util.ComponentUtilities.setServerContextRoot(ComponentUtilities.java:337)
at org.jboss.tools.openshift.express.internal.ui.wizard.appimport.ServerAdapterFactory.renameWebContextRoot(ServerAdapterFactory.java:101)
at org.jboss.tools.openshift.express.internal.ui.wizard.appimport.ServerAdapterFactory.createServerAdapter(ServerAdapterFactory.java:83)
at org.jboss.tools.openshift.express.internal.ui.wizard.appimport.ServerAdapterFactory.createServerAdapter(ServerAdapterFactory.java:75)
at org.jboss.tools.openshift.express.internal.ui.wizard.appimport.ServerAdapterFactory.create(ServerAdapterFactory.java:54)
at org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizardModel.createServerAdapter(OpenShiftExpressApplicationWizardModel.java:196)
at org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizardModel.importProject(OpenShiftExpressApplicationWizardModel.java:94)
at org.jboss.tools.openshift.express.internal.ui.wizard.OpenShiftExpressApplicationWizard$ImportJob.runInWorkspace(OpenShiftExpressApplicationWizard.java:274)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
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, 10 months
[JBoss JIRA] (JBIDE-11736) "Project Archives" explorer is still visible in project explorer
by Jaroslav Jankovič (JIRA)
Jaroslav Jankovič created JBIDE-11736:
-----------------------------------------
Summary: "Project Archives" explorer is still visible in project explorer
Key: JBIDE-11736
URL: https://issues.jboss.org/browse/JBIDE-11736
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Archives
Affects Versions: 3.3.0.Beta3
Reporter: Jaroslav Jankovič
Assignee: Rob Stryker
Fix For: 3.3.0.Beta3, 3.3.0.CR1
After I create jar archive of project and place it in project location, there is new "Project Archives" explorer in Project Explorer. After I delete all archives in this explorer, explorer is still visible under project. I think there is no need to "Project Archives" be still visible, if there are no archives in project. It should be visible only if there is at least one archive located under specific project.
--
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, 10 months