|
Description
|
------------------------READ-ONLY BUG REPORT---------------------------
This bug is a read-only copy of the netbeans.org bug #21963 at:
http://www.netbeans.org/issues/show_bug.cgi?id=21963
This bug will be updated daily with edits made there.
------------------------READ-ONLY BUG REPORT---------------------------
xxxxx@xxxxx , 2002-03-29 01:00:27 :
This RFE is addition to issue
http://openide.netbeans.org/issues/show_bug.cgi?id=21811
Would be better, if user will be able specify servlet-name
(or this name will be generated at this stage) in New WIzard.
xxxxx@xxxxx , 2002-03-29 01:01:38 :
Correct summary
xxxxx@xxxxx , 2002-03-29 01:14:52 :
It is possible to specify name on the last panel of wizard but we need
to make it more robust and check cases when element with given name
already exists and avoid overriding of user's data.
One suggestion is to keep this entry empty (or diplay<default value>)
and substitute unique value here during instantiation of customer
together with checking for uniqness that will disable finish button if
users insert already existing name.
======================================================================
xxxxx@xxxxx , 2002-05-01 09:47:43 :
I don't like the idea of disabling finish in the case of a
duplicate name appearing. My personal feeling is that the
check should be perform when the user clicks finish, at
which point they are given a confirmation dialog indicating
that this servlet name already appears in the deployment
descriptor. Then the user can choose one of two actions:
1. Confirm overwrite. The servlet is created and the entry
in the deployment descriptor is overwritten.
2. Cancel. The user would then be returned to the new
servlet wizard to edit the servlet name.
This would need input from HIE, but from a QA perspective,
this is how I would think it should work. Simply disabling
the finish button when the servlet matches a name which
already exists requires real-time checking and could be
confusing to the user because they won't immediately know
why the Finish button is disabled.
xxxxx@xxxxx , 2002-05-01 09:48:28 :
Adding John Baker to the CC list.
xxxxx@xxxxx , 2002-05-01 10:06:57 :
I agree with Jason. Disabling the Finish button in this
instance does not clearly indicate what the issue might
be--there are too many values on this panel.
I'm not sure of the user scenarios where I'd want to overwrite
existing servlet deployment descriptor data while creating a
new servlet, so at a minimum, I would expect the name checking
to occur when I hit the"Finish"button and then have the
opportunity to change the servlet name or cancel the creation.
xxxxx@xxxxx , 2002-05-01 12:28:34 :
Also, the following bug describes why we don't want to just disable
the finish button if the servlet name is not unique:
http://www.netbeans.org/issues/show_bug.cgi?id=11694
Bug End:
======================================================================
xxxxx@xxxxx , 2002-07-22 04:11:28 :
Set target milestone to TBD
xxxxx@xxxxx , 2002-07-22 04:21:15 :
Set target milestone to TBD
Bug End:
======================================================================
xxxxx@xxxxx , 2002-08-05 09:54:20 :
Passing to new owner
Bug End:
======================================================================
xxxxx@xxxxx , 2003-11-24 17:39:15 :
I have modified the servlet wizard in such a way that it checks
whether the name is used. This uses the same mechanism as for all
other input validation: if the input is invalid, finish is disabled
and we show a message describing the problem at the bottom of the
wizard.
This will be implemented for the filter case later. QA, please test
for servlet.
Bug End:
======================================================================
xxxxx@xxxxx , 2004-01-06 12: customer :36 :
Fixed for servlets and filters.
Bug End:
======================================================================
|
