"Products.GenericSetup.OFSP.exportimport.FolderXMLAdapter._{ex|im}portNode" ineffective
Bug #448780 reported by
Dieter Maurer
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zope CMF buildout |
Invalid
|
Undecided
|
yuppie |
Bug Description
"FolderXMLAdapter" defines its own "_exportNode" and "_importNode" but they are not used in the "INode" interface because property "node" is not redefined with this new definitions and therefore continues to use the one from "Products.
Changed in zope-cmf: | |
assignee: | nobody → yuppie (yuppie3) |
To post a comment you must log in.
'_exportNode' and '_importNode' solve the same task in XML adapters and pure node adapters. That's why those methods have the same name in both kinds of adapters. But they are used differently: XML adapters call them from '_exportBody' and '_importBody', pure node adapters use them for the 'node' property.
XML adapters need to export and import 2 different nodes for each object: One simple node that's part of the parent's XML file. And one complete node that's stored in the object's own XML file.
Only pure node adapters should redefine the 'node' property.