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 81512 - Refactoring makes schema invalid
Summary: Refactoring makes schema invalid
Status: VERIFIED FIXED
Alias: None
Product: xml
Classification: Unclassified
Component: Schema Tools (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Nam Nguyen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-31 16:40 UTC by Ivan Sidorkin
Modified: 2006-09-14 16:10 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 Ivan Sidorkin 2006-07-31 16:40:09 UTC 
build 20060730

- create Java Application
- add new Purchase Order schema
- In schema view select Elements->purchaseOrder
- copy purchaseOrder
- paste it in the same place
- purchaseOrder1 added
- in context menu for purchaseOrder1 select Refactor->Rename...
- change name from purchaseOrder1 to purchaseOrder
- press Next button
- press Do Refactoring button 

now schema has two purchaseOrder elements, so it's invalid
Comment 1 Chris Webster 2006-07-31 16:42:22 UTC 
Should do a duplicate check. I am making this a P3 as we should do this for FCS,
but not a showstopper for beta.
Comment 2 Ivan Sidorkin 2006-08-10 21:52:17 UTC 
Duplicate check is not enough.
need check for valid name before allowing to press next button in rename dialog
and at pressing enter in properties editor.
Comment 3 Chris Webster 2006-08-10 23:54:24 UTC 
name must be valid as well. I had assumed this was already being done, if not
this is necessary also.
Comment 4 Nam Nguyen 2006-09-09 01:23:30 UTC 
Duplicate and non-NCName are checked as part of rename refactoring now.
Comment 5 Ivan Sidorkin 2006-09-14 16:10:07 UTC 
verified in 060911