This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
dev build 200409121800 JDK 5.0 RC I configured my external Tomcat 5.5.1 server as the default server under the Runtime tab, yet when I run my code the built-in server is still getting invoked. This is further complicated by the fact that Tomcat 5.5.1 incorporates changes that makes XML configuration files not backwards compatible with 5.0, so my 5.5-specific XML files refuse to run on the 5.0 server. Please try to provide me with a workaround in the meantime.
And while we're on the topic, there is no indication of which server is the default. I expect to see this indicated in the icon or name somehow.
Two issues: 1) We should take a look at issue #37069 which seems to be related to this issue and resolve it if possible. 2) I found out that the Tomcat server used is a project-setting. I therefore propose we remove the ability to set a Tomcat server as "default" because all it seems to do is lead to confusion. There should only be one place to configure which server gets used. The problem is, I'm still unable to get Tomcat 5.5 up and running. The error I get now is: init: deps-jar: init: deps-jar: compile: jar: compile: compile-jsps: run-deploy: In-place deployment at C:\Documents and Settings\Gili\My Documents\scp\com\tog\desktopbeautifier1\DesktopBeautifierServer\build\web deploy?config=file:/C:/Documents%20and%20Settings/Gili/My%20Documents/scp/com/tog/desktopbeautifier1/DesktopBeautifierServer/build/web/META-INF/context.xml&war=file:/C:/Documents%20and%20Settings/Gili/My%20Documents/scp/com/tog/desktopbeautifier1/DesktopBeautifierServer/build/web/ FAIL - Invalid context path null was specified FAIL - Invalid context path null was specified C:\Documents and Settings\Gili\My Documents\scp\com\tog\desktopbeautifier1\DesktopBeautifierServer\nbproject\build-impl.xml:283: org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment$DeploymentException: Deployment Error BUILD FAILED (total time: 0 seconds) This seems to be outside my control. Is there a workaround/fix for this issue?
Looks to me like we're issueing a "deploy" command to the Tomcat manager but not specify a "path" argument which is required. Not sure why this works for the built-in server. Can anyone comment?
This is because of changes in deploy task notation between 5.0.x and 5.5.x - please note that nb 4.0 does not support Tomcat 5.5.x - the way you could utilize it with your web app is the project with existing ant script.
Martin, I've got a web application with an ant-script generated by Netbeans. Which part of the script would I modify to make it work under Tomcat 5.5? Also, what would I need to change in the deploy command arguments? I took a quick look at the documentation and did not notice any differences. Thanks, Gili