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 71021 - display_name_changed event causing config file to be marked dirty.
Summary: display_name_changed event causing config file to be marked dirty.
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: _ pcw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-05 01:01 UTC by _ pcw
Modified: 2006-01-24 13:27 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description _ pcw 2006-01-05 01:01:22 UTC 
The DISPLAY_NAME_CHANGED event proprogated by the DConfigBean tree is causing
the configuration to be marked dirty, thus requiring a save, even though this
event does not represent a change of any data.  It is merely a UI event sent to
indicate that the displayed name of node in the explorer side of the
configuration has changed.

To reproduce, create a web application with a resource-ref, edit the
configuration and delete the JNDI name of the resource.  Save the configuration,
close it, then reopen it.  Now select the resource-ref customizer and upon the
display of this customizer, the configuration will be marked dirty.  This is
because the validator for the JNDI name attempts to change the name of the node
to indicate that the resource-ref is invalid (due to not having a JNDI name).