- This topic has 4 replies, 1 voice, and was last updated 21 years, 1 month ago by
.
-
Posts
-
When creating a new deployment, I select from the drop down the server I want to use but the location is left empty. Even if I fiddle with the options in the drop down, exploded or not, etc. the location is always empty (which makes it impossible to “finish”).
E 2.1.2
ME 2.7RC2
Sun JDK 1.4.2_02
Linux 2.4.24 KernelNOTE. When I select “packaged” the “finish” button becomes enabled, although the location is still empty. So I hit “finish” and now I have a deployment listed for my project that I cannot remove and it has an empty location. The deployment tool complains now that I don’t have any valid (enabled) app servers, but I’ve double checked that setting (Tomcat 5) twice already and its enabled. I’ve also tried disabling (apply) and then reenabling it to no avail.
Is there a way to manually clear out this deployment target somehow so I can try to recreate it?
UPDATE: Restarting Eclipse seems to have cleared the invalid deployment entry, but I am still unable to create a valid one (the location is still always empty).
UPDATE: It seems at some point (possibly AFTER adding struts capabilities to my project) that my webroot was reset to just /, this was causing the deployment tool to fail. I would have the following suggestions for handling this:
1) Provide a warning when using the deployment tool that the project you are attempting to setup a deployment for has a webroot of “/”. If this is invalid, let the user know they need to change it. if this IS valid, then the deployment tool should honor it (and deploy to whatever / would resolve to w.r.t. to that app server)
2) When Editing a project properties, provide a popup that the webroot is invalid (assuming / is an invalid web root).
Scott/Michael please feel free to close this after you’ve evaluated the possible solutions to this problem and optionally filed them.
