You need to set up a configuration for your server. Go into Debug (not the Debug => [yourappname]), but the proper debug. Create a new config here, and then you deploy, you should have the name of the configuration showing up on the list.
By "Go into Debug ... the proper debug" do you mean from Eclipse invoke the menu item "Run" | "Debug...", then from the "Debug" (create, manage, and run configurations) dialog select "JBoss 3.2.x" and click "New"?
If so, I have created a new configuration with the following settings:
"Home" tab: JBoss 3.2.x Home Directory: "D:\jboss-3.2.6"
"Start" tab: Program arguments: ""; VM arguments: "-Xmx512M -Xincgc"
"Shutdown" tab: Program arguments: "-S"; VM arguments: ""
"Log Files" tab: [none]
"Source" tab: 9 .jar files under "Default", and "org.jboss.ide.eclipse.jdt.core.classpath.j2ee-1.3"
"Classpath" tab: the bootstrap entry: "JRE System Library [j2sdk1.4.2_06]"
"JDK" tab: the Runtime JRE selected is "Workspace default JRE (j2sdk1.4.2_06)"
but I had a similar debug configuration already.
This starts JBoss seemingly successfully as detailed earlier, but still nothing happens when I click the "Deploy To..." menu option of my .ear (app) file.
Under Eclipse, Window | Preferences | JBoss-IDE | Deployer results in the showing of an error dialog. Perhaps this indicates a problem which I have with my installation.
Also, it looks like my choice of Source as "org.jboss.ide.eclipse.jdt.core.classpath.j2ee-1.3" should be for 1.4 instead.
I have now reinstalled Eclipse and JBoss as per my earlier settings (using JBoss-IDE 1.3.30) since I need the "Undeploy" pop-up menu option to be enabled once I have deployed. This particular bug is listed but no one is down to fix this yet.
Thank you for your help.
No problem. Now, if only I could get someone to help me with my problem.... ;)