XML Attributes Created Twice in the XML after Saving in FM

Question

Hi All,
I've built a structured application to read and write a custom XML. The file is opened just fine. However, when saving the XML in FM, some XML attributes appear in the XML twice. For example, in the original XML I have the following:
<object_group doc_name="xxx" parsed_by_sym="false">
</object_group>
After I save the XML, it looks like this:
<object_group doc_name="xxx" parsed_by_sym="false" doc_name="xxx" parsed_by_sym="false">
</object_group>
After the XML is saved, FM refuses to re-open it aborting the parsing. If I remove the doubled attributes manually in Notepad, then the XML is opened in FM again.
Should I define anything in read/write rules? What am I doing wrong?
I'm using an XSD, which I defined in structapp.fm.
Thank you very much!

Answer 1

Alex,
  Without looking at the application and document, I don't have any other ideas. To debug a situation like this, I would try variations such as the following, investigating any change that eliminates the doubled attribute:
1) If you haven't already, shut your computer down and restart it.
2) If the application uses a custom client or processing, remove them. If their absence makes a difference, the problem may originate in them.
3) Simplify the test document as much as possible, probably in several steps. For example, remove all optional attributes and elements. Remove all non-containers (tables, xrefs, graphics, etc.) You may need to change the EDD or schema to create as short a document as you can that fails. The goal is to have a document with just a few elements and only one attribute that fails.
4) Change the element and attribute names, which shouldn't make a difference, but may be worth testing.
5) Simplify or eliminate the r/w rules.
6) Simplify the EDD so that the only defined elements and attributes are the ones that appear in the small sample.
7) Remove all format rules and autoinsertions from the EDD. The goal is to remove anything that should not be relevant.
8) Simplify the schema in the same way.
9) Remove the schema from the application. If doing so eliminates the duplicate, convert the schema to a DTD and see if using a DTD instead of the schema makes a difference.
10) Make sure your have installed all updates to the version of FM you are using.
11) If you have access to a different version of FM, see if it behaves the same way.
Good luck and let us know when you find the problem.
     --Lynne