This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 305785 - Unable to run XHTML file on Server
Summary: Unable to run XHTML file on Server
Status: RESOLVED FIXED
Alias: None
Product: WTP ServerTools
Classification: WebTools
Component: wst.server (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: 3.2 M7   Edit
Assignee: Angel Vera CLA
QA Contact: Angel Vera CLA
URL:
Whiteboard:
Keywords:
: 292551 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-03-13 19:13 EST by Raghunathan Srinivasan CLA
Modified: 2017-10-11 16:32 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Raghunathan Srinivasan CLA 2010-03-13 19:13:59 EST
I was not able to reproduce this when I tried again in a new ws, but here are the steps:

1) Launch Eclipse on a new workspace
2) Define Apache Tomcat as the Server
3) Create a DWP with JSF 2.0 facet
4) Create a XHTML file.
5) Publish the app on  the server.
Result: The page is not launched in the internal browser. The following exception is logged.


eclipse.buildId=I20100312-0800
java.version=1.6.0_17
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86


Error
Sat Mar 13 14:55:57 PST 2010
Could not launch Run on Server

org.eclipse.core.runtime.CoreException: Local configuration cannot be nested in a directory.
at org.eclipse.debug.internal.core.LaunchConfigurationType.newInstance(LaunchConfigurationType.java:460)
at org.eclipse.wst.server.ui.internal.actions.RunOnServerActionDelegate.getLaunchConfiguration(RunOnServerActionDelegate.java:534)
at org.eclipse.wst.server.ui.internal.actions.RunOnServerActionDelegate.run(RunOnServerActionDelegate.java:332)
at org.eclipse.wst.server.ui.internal.actions.RunOnServerActionDelegate.run(RunOnServerActionDelegate.java:689)
at org.eclipse.wst.server.ui.internal.ServerLaunchShortcut.launch(ServerLaunchShortcut.java:41)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.launch(LaunchShortcutExtension.java:434)
at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.run(LaunchShortcutAction.java:73)
at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.runWithEvent(LaunchShortcutAction.java:121)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1050)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1074)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1059)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:773)
at org.eclipse.jface.action.ActionContributionItem$9.handleEvent(ActionContributionItem.java:1284)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1050)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4037)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3628)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2416)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2380)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2229)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:504)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:497)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
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:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1406)
Comment 1 Angel Vera CLA 2010-03-13 20:38:34 EST
This might be related to the old workspace that was being used, but not sure what could had failed. Passing to the debug component for assistance
Comment 2 Darin Wright CLA 2010-03-14 11:22:50 EDT
We recently fixed a bug in the platform that allowed clients to create local launch configurations with slashes (i.e. directory paths) in the names. This caused the configuration to be created in a subdirectory in workspace metadata. Such configurations will never be found by the platform after a workspace re-start. The platform now throws an exception for invalid configuration names.

See bug 275741 that describes the fix. Clients should not be doing this.

Moving to WST in case they want need adjust code on their end.
Comment 3 Angel Vera CLA 2010-03-18 12:46:28 EDT
*** Bug 292551 has been marked as a duplicate of this bug. ***
Comment 4 Angel Vera CLA 2010-04-05 13:38:36 EDT
Changes committed into HEAD
Comment 5 Angel Vera CLA 2010-04-06 18:18:04 EDT
Changes released to HEAD
Comment 6 Angel Vera CLA 2010-04-06 18:20:40 EDT
Marking as fixed
Comment 7 Eclipse Genie CLA 2017-10-11 16:32:01 EDT
New Gerrit change created: https://git.eclipse.org/r/108895