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.
Bug exists in Build 020225_2 (EA) with jdk1.4. It's impossible to select "localhost" Tomcat server instance created in another Service entry as a target server for the Web Module. How to reproduce: 1. Add new Service entry to the server.xml file. E.g. it may look like this: <Service name="Tomcat-Service-1"> <!-- Define a non-SSL HTTP/1.1 Connector on port 8080 --> <Connector className="org.apache.catalina.connector.http.HttpConnector" port="8083" minProcessors="5" maxProcessors="75" enableLookups="true" redirectPort="8443" acceptCount="10" debug="0" connectionTimeout="60000" /> <!-- Define the top level container in our container hierarchy --> <Engine name="Tomcat-New-1" defaultHost="localhost" debug="99"> <Host name="corvus.eng" appBase="webapps"> </Host> </Engine> </Service> 2. Add new host in this service 3. Mount some web module with e.g. some JSP in it and try to select newly created TC server instance as a target server and execute the JSP on it. Notice that new context is always added to the instance in the Tomcat-Netbeans service rather than in newly created one and external browser is always started with the port number of the server instance in Tomcat-Netbeans service.
I cannot reproduce this bug. See my test flow : - I added the Tomcat-Service-1(which is declared above) to the server.xml file (manually to the internal Tomcat40 installation) - than I created several hosts in this service(engine) - I played with setting of different hosts as a default web server instance and tried to execute my web module with the default web- server option - I also played with setting different Tomcat4.0 Hosts for the Web module:Target Server Property. Everything was running perfectly. You should describe more detaily how did you create new hosts and how did you exactly execute your web module. Possibly send me your server.xml file.
I forgot to mention that problem occurs when one tries to select target server via combo box rather than via Property Editor. Create two "localhost" Hosts entries in different Services and then try to select one of them and then another one using property combo box and notice that one of them remains always selected despite your choice.
Fixed for FCS. Tomcat4.0 instance is now specified by : - installation name ("Internal" or path) - host name - service name
Verified in Build 020315.