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.
1. Start NetBeans 4.0 with Sun AppServer plugin or use NetBeans 4.1 ea1. 2. Set AppServer as default server. 3. Create new web project. Now AppServer should be target server for this new project, but it isn't. Let the target server field empty for now. 4. Run project. A dialog appers and you can choose which server to use, but AppServer is missing, only Tomcat is there.
Does not affect the NB 4.0 release, adding the NO40 keyword.
Do we need to investigate whether this would affect the bundled AS plugin?
Libor: this test case works for me with NB trunk code and latest AS plugin in cdp-j2ee build. Which appserver plugin do you use? Any stack trace in messages.log to help debug?
Now I found out that it happens only when you create sample projects (New Project -> Samples -> 'Web', 'Enterpise' or 'Java BluePrints Solutions')
Yes I can reproduce this with Sample/TomcatJSP eventhough the configuration is created properly for the default Tomcat instance. Interesting thing is that this does not happen to plain webapp and only to sample web projects. If we have Sample web projects then this should be fixed?
will resolve for 4.1
Their default value should be 'default server' or 'Tomcat 5.5.x'. Currently it's Tomcat 5.0.x which will cause "Server Reference Problem" implemented by Stepan.
Fixed in trunk
verified