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: | setModified does not work in XMLMV | ||
|---|---|---|---|
| Product: | xml | Reporter: | scanti <scanti> |
| Component: | XML Multiview | Assignee: | Svata Dedic <sdedic> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | blocker | CC: | pjiricka |
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Bug Depends on: | 77210 | ||
| Bug Blocks: | |||
The fix looks fine. It can be integrated, I think. bad tm value... reset to tbd The save support in the platform is a real mess. I am wondering whether the proposed Savable interface would help here. See issue 77210. Should work fine, current implementation (indirectly) calls DO.setModified(false) through XmlEnv. Please check in 7.1 dev/beta builds |
I am currently developing an RCP that uses XML-Multiview I have found this problem. If I call setModified(true) on the dataObject, the first time every thing works. Then I click on the save button and recall setModified(true). This time I am not able to save unless I go to the Text view and I press any key I have found a workaround by extending XmlMultiViewEditorSupport and adding @Override public void saveDocument() throws IOException { super.saveDocument(); DataObject dataObject = getDataObject(); if(dataObject.isModified()) { dataObject.setModified(false); } } I will be grateful if you could fix it Thanks