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.
Summary: | Servlet mapping broken for updating changes to servlets | ||
---|---|---|---|
Product: | javaee | Reporter: | John Baker <jbaker> |
Component: | Code | Assignee: | Petr Pisl <ppisl> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | cfqacore |
Priority: | P4 | ||
Version: | -S1S- | ||
Hardware: | Sun | ||
OS: | SunOS | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
John Baker
2003-05-13 22:31:21 UTC
I agree that it is confusing that the URL pattern is not updated. Perhaps we should default it to something better that string containing class name. We refused to update because it can break other parts of web app and it will work without modification. Deleting works for me (both servlet and servlet-mapping is deleted). What's annoying with the dialog? Closing as won't fix according to previous comment unless you convince me that there is strong reason to change current behaviour. BTW: servlet support will be significantly reworked for 4.0 The dialog is annoying since clicking the Process All button doesn't do anything and it pops up for every servlet that is renamed. Why have this dialog open if nothing is changed? Deleting a servlet _doesn't_ delete the mapping. If this can't be fixed in this release, move this to the next release. > The dialog is annoying since clicking the Process All button > doesn't do anything and it pops up for every servlet > that is renamed. Why have this dialog open if nothing is changed? OK. So there can be servlet source that doesn't have servlet/servlet-mapping in web.xml and triggers this dialog. This might be a usability problem but definitely not a P2 bug. Is this your case? Coalescing of changes sounds like RFE to me. > Deleting a servlet _doesn't_ delete the mapping. cannot reproduce Works fine in NetBeans 4.0. Marking as Fixed. |