- This topic has 8 replies, 2 voices, and was last updated 17 years, 7 months ago by
.
-
Posts
-
All,
I’m running into a new problem deploying to a JBoss server. This had been working just fine before this series of events:
1) Installed the Perforce Eclipse plugin (P4WSAD) under Eclipse (not ME)
2) Ran into some issues the next time I restarted ME.
3) Ran ME again with -clean option. Still not so good.
4) Switch to a new workspace. Still no luck.The symptom I’m seeing is that even though I reconfigured the JBoss server in ME, it seems that ME doesn’t know where to deploy apps under the JBoss server. In the Manage Deployments dialog, I select the server and the app, but the deployment location remains empty.
Got any ideas?
-jc
Perhaps this might help. An excerpt from the Eclipse error log:
java.lang.NullPointerException
at org.eclipse.core.runtime.Path.<init>(Path.java:152)
at com.genuitec.eclipse.ast.deploy.core.DeploymentManager.computeDeploymentLocation(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ui.wizard.NewDeploymentWizardPage.updateLocationField(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ui.wizard.NewDeploymentWizardPage.handleServersComboBoxModified(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ui.wizard.NewDeploymentWizardPage$2.modifyText(Unknown Source)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:196)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:933)
at org.eclipse.swt.widgets.Combo.wmCommandChild(Combo.java:2203)
at org.eclipse.swt.widgets.Control.WM_COMMAND(Control.java:3375)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3249)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4025)
at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method)
at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:1844)
at org.eclipse.swt.widgets.Combo.callWindowProc(Combo.java:281)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3334)
at org.eclipse.swt.widgets.Combo.windowProc(Combo.java:1921)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4025)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1925)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2966)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
at org.eclipse.jface.window.Window.open(Window.java:796)
at com.genuitec.eclipse.ast.deploy.core.ui.dialog.DeploymentManagerDialog.Ă(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ui.dialog.DeploymentManagerDialog.access$1(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ui.dialog.DeploymentManagerDialog$4.handleEvent(Unknown Source)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
at org.eclipse.jface.window.Window.open(Window.java:796)
at com.genuitec.eclipse.ast.deploy.core.ui.action.ManageDeploymentsAction.basicRun(Unknown Source)
at com.genuitec.eclipse.core.ui.action.LicenseValidatingAction.run(Unknown Source)
at com.genuitec.eclipse.core.ui.action.LicenseValidatingAction.runWithEvent(Unknown Source)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
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.core.launcher.Main.invokeFramework(Main.java:336)
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)I see from today’s announcement that you folks have been busy getting 5.5M1 out the door. Which I think is great, but I still need some guidance on this one. Even if you could simply explain how ME constructs the deployment folder for apps (andfiles involved), I can start tracking this down myself.
-jc
The symptom I’m seeing is that even though I reconfigured the JBoss server in ME, it seems that ME doesn’t know where to deploy apps under the JBoss server. In the Manage Deployments dialog, I select the server and the app, but the deployment location remains empty.
Ahh, check your project’s properties, go under MyEclipse > Web and make sure your web root context has a value in it like /myapp, sometimes plugin conflicts can cause that box to empty out.
Doh, hey I’m sorry for not answering this sooner. If that happens again, PM me to make sure I see this.
Don’t sweat it. All has been returned to normalcy.
Now, as Marge would say, “Let’s never speak of this again.”
