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.
Open visual editor for context.xml, click to Context Path field and type some text. Don't click to another place, just close editor. You will not be asked whether to save changes and changes will be lost. If you click in editor to another place after the change then file is marked as modified and you will be asked to confirm changes. This issue is similar to issue #55082 fo DD.
The problem is in j2eeserver (or j2eeeditor). Tomcat does not provide this UI. Is works for app server, because it updates the beans as the user is typing, but the config editor only updates when the property is updated.
(this works for AS plugin because it uses customizers)
I realize that this is how the property sheet behaves _everywhere_ else in IDE. I do not think this is something I need to workaround. See: 1. open Properties for a file, type in a different name, click [x] to close it - data lost 2. properties window for form objects - change a tooltip text, for example, and close the property sheet w/o clicking anywhere - data lost 3. customizer of grid back layout - it embeds property sheet - change a value and close the dialog - data lost 4. Tools | Options - again I could go on forever. So.... I think this is in fact not a defect, it is a user error. Property sheet behaves like this consistently. When you type a string value simply hit the Enter key at the end, please.
I agree with Pavel. Removing fix-in-41. Libore speak up if you disagree.
Very bad NetBeans behaviour... We have a P2 on that: 57473 Should we write our own stringprop editor that listen to every key stroke?
It is really the same problem in 57473? It is not clear from the description. Anyway, I was looking for another product that uses property sheet. I found one (I will not name it, but it's a tool that is not based not netbeans). This one updates the property when you leave the property editor. When the property editor is in an editor it shows a "save/discard" dialog. If it is just a properties window it updates the property w/o asking. That's ok with me if we do the same in property editors, I just do not want to workaround it in one place.
The behaviour of property sheets is bad in general, it needs to be fixed in the future (this is not the only issue, a discussion has been started on an xdesign maillist). With regards to this issue (P2) and issue #57473 (P3): * shouldn't the priorities be the same? * could we fix all property sheets for 4.1? * if not, can we waive 57473 and fix locally the context.xml property sheet (which looks like and editor, but does not behave like that) Adding Ludo and Peter J. on CC to make comments.
!!! Please, disregard my previous comments! !!! I realized that the property sheet issue really is not the basic of #57473. On the other hand, this issue is caused by a property sheet bug. *A value of a sheet cell should be committed when the property sheet window is being closed.* Why did you Pavle set this to WONTFIX? I think we (I) should file a bug against the property sheet and set this as dependant or invalid. Anybody has a clue what is the property sheet's module?
We need a fix in NB 4.1 FCS... issue #57473 is a P2, not a P3 bug...
see 57560 for the general problem in openide | property sheet
reopening, issue 57560 is resolved but it does not solve this problem
Stepane, this should go away when 62787 is fixed, right?
Yes, we can close this issue when issue 62787 is fixed.
-> WONTFIX, since the visual context.xml editor is no longer used