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.
This means that neither NB 3.5 nor NB 3.6 can be used to develop web services... The UI should make it clear what criteria are used to determine the version and allow the user to override the decision that the plugin made. This is probably a P1.
Pavel B says the criteria is whether there is a bin/catalina.xml file. "touch catalina.xml" works, or whatever the dos equivalent is a workaround for this problem.
One think we can do is to add a description of this problem together with a workaround into release notes. The workaround is quite easy: Create a dummy file catalina.xml in $JWSDP_HOME/bin and create a directory named temp directly in the $JSWDP_HOME directory. The problem is that we have never tested this combination (IDE+JWSDP) before and since we are out of resources we wont be able to do so for promo-B. I have tried to conform the JWSDP installation with the IDE -requirements- and encountered a few differencies/problems with the integration in a very short time. The integration itself works, but I have seen some other bugs. The question is if want to encourage users to use the JWSDP since we are not sure if it's safe. Maybe, it would be better to say: it's -unsupported- and not tested, but if you really need to do it, there is a workaround how to do that.
Waiver approved.
Chris, could you provide the wording for this one?
For release notes: Description: If you try to add JSWDP 1.3 Tomcat using the Add New Server action, the dialog will not let you add it because it does not recognize the installation as a Tomcat 5 server. Workaround: Do the following steps so that the Add New Server dialog box recognizes the installation as a Tomcat 5 server. 1. Add a directory to <JWSDP-Install-Dir> named temp. 2. Add a file to <JWSDP-Install-Dir>/bin named catalina.xml. NOTE: The JWSDP Tomcat server has not been tested with this version of the IDE and its use is not supported.
BTW, JWSDP 1.4 is now released, we should target this release.
This bug seem to be already fixed. I've tested it with tomcat-jwsdp-1.4 and it works fine.
Verified