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: | Deleting a WSDL component then invoking Save throws NPE | ||
---|---|---|---|
Product: | xml | Reporter: | pvarghese <pvarghese> |
Component: | WSDL Tools | Assignee: | Nathan Fiedler <nlfiedler> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | ||
Priority: | P1 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
pvarghese
2007-02-07 22:31:48 UTC
It seems that selecting any node and deleting it, then invoking Save will result in an NPE. The priority should be raised. BTW, I have a fix for this, but the problem then becomes, the SaveCookieDelegate will not actually save because the Node's component is no longer in the model. Need a fool-proof way to get the DataObject and be able to save the document. NPE that appears in a dialog is a P1. Fixed in release551, in that the NPE no longer occurs. However, the Save is still not successful until the user selects another node. Will enter another issue for this, with appropriate priority. wsdlui/src/org/netbeans/modules/xml/wsdl/ui/view/treeeditor/WSDLElementNode.java; new revision: 1.1.2.26.4.9; previous revision: 1.1.2.26.4.8 Verified on Windows XP with Gavotte 070216_24 and JDK 1.5.0_09 that the scenario no longer produces an NPE. The Save issue that I planned on entering turned out to have been entered already. See issue 94899 for the full description. |