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.
Summary: | XML schema elements can not be deleted or renamed | ||
---|---|---|---|
Product: | xml | Reporter: | Oleg Barbashov <obarbashov> |
Component: | Code | Assignee: | Sonali Kochar <sonali> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | CC: | hong_lin |
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Oleg Barbashov
2007-03-20 13:41:43 UTC
5. Double click on element to rename it. Enter new element's name and press enter. Changes in name is discarded. This bug blocks Loan Processing blue print sample tutorial development. Please fix it as soon as possible. Since this is a regression bug, the priority is upgraded. I don't understand why this is schematools bug? Just from the stack trace i would say that this issue is dual but not within xml/refactoring or ABE control. First, the NB refactoring API itself should handle bad refactoring plugin registrations such that one should not affect functionality of the rest. WSITRefactoringFactory is owned by websvc team. (i) The stack trace is coming from Websvc code, however it shouldnt affect the refactoring functionality. Please see issue#98387 :: WSITRefactoringFactory throws a ClassNotFoundException (ii) I have filed a separate bug for the "Delete" action. Please see issue#98568::XML Schema elements cannot be deleted in Design view (iii) I have fixed the unable to rename element in Design view issue as reported in this bug. The code was putback in build number# 070321_9 Testing:: 1. Open a new BPEL project. 2. Add the XML schema and open it in the Design Mode. 3. Double click on element to rename it. Enter new element's name and press enter. Result:: The element should be renamed. Verified the fix is in Hual daily build 200703220921 |