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.

Bug 41885 - Table-view editor cannot save keys containing space
Summary: Table-view editor cannot save keys containing space
Status: RESOLVED FIXED
Alias: None
Product: utilities
Classification: Unclassified
Component: Properties (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jan Stola
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-09 13:40 UTC by Marian Petras
Modified: 2004-08-13 12:11 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marian Petras 2004-04-09 13:40:15 UTC
If a key containing a space character is entered
in the New Property dialog, the space is badly
converted and is considered to be a separator
between the key and the value.

Steps to reproduce:
1) Open an existing or create a new Properties
   file using action Open (so that a table view
   is open).
2) In the editor, click on button
   "New Property...".
3) In the New Property, enter key "my key" and
   value "my value". Press the OK button.

A row is added to the table. But the key and value
differ from what was entered in the dialog:

    key ..... "my"
    value ... "key=my value"
Comment 1 Marian Petras 2004-04-09 13:42:58 UTC
The cause of this bug is that the key is converted using function
UtilConvert.saveConvert(...) which does not escape (precede with a
backslash) the space character. When the key-value pair is read, the
space between "my" and "key" is treated as a key-value separator.
Comment 2 Jan Stola 2004-06-08 15:17:45 UTC
Fixed - a space in a key is escaped by a backslash by now.
Comment 3 _ proxity 2004-07-20 12:03:13 UTC
Fixed where? I've got 3.6 with all updates and hotfixes applied. It
still doesn't work.

Comment 4 Jan Stola 2004-07-20 12:30:57 UTC
See Target Milestone: promo-D e.g. it will be fixed in Netbeans 4.0.
It is fixed in the development builds by now - we don't create/provide
patch for each bug fix.