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.
[010418_2] If you set the URI property of a webmodule and then execute the webmodule or a JSP page from it everything works fine - URI is applied and root of the webmodule is mapped to the URI. When you change the URI and execute the webmodule again it still use old URI.
Target milestone -> 3.3
If you change Webmodule URI then new URI is added, but all old URIs remains and they are still applicable. Old URI should be deleted.
Old URI should NOT be deleted. It is requried feature (ask George Fink for more informations). *** This issue has been marked as a duplicate of 12180 ***
-
- *** This issue has been marked as a duplicate of 11741 ***
If old URI should not be deleted then UI for this property is badly designed. If user change URI in string property then he will expect that the URI is really changed, not new URI added. The property editor for editing array of strings would match better for this feature, but it would not look good.
The opinion of the majority of people is that when a web module is deployed to the server, this deployment should be "permanent", so when the module is deployed with another URI, this does not affect this previously deployed module (unless there are conflicts). In other words, the IDE does not necessarily know about all modules deployed to the server, it only knows about the module (mapping) that the user is currently working with. So there is no requirement that the IDE knows about all the URIs that a module is deployed with.
OK, it seems reasonable.