LVOOP to XML misleading behaviour

[Phil Duncan]

Hi all,

I have been working on a project that warranted saving data as XML. I am using LV 8.5 and have implemented LVOOP classes in the project and developed the code to flatten the class data (actually an array of classes) to xml. No broken wires and things are going fine. When I started testing, I found that LV could write the flattened (array of classes) to an xml file that I could open in a browser and confirm was a complete record of the class array. Unfortunately, when I tried to unflatten the xml file I got nothing. After a little investigation I discovered the following:

In LV 8.5 you CAN'T wire a class to the flatten to XML primitive.

In LV 8.5 you CAN wire an array of classes to the flatten to XML primitive.

Here is the resulting XML string output.

And when you try to unflatten the XML data you get the following msg.

Overall I have found the inconsistant behaivour quite annoying, and the de-bugging time was frustrating also. Incidently, in LV 8.2 you cannot wire either a class or an array of classes (as above) to the flatten to XML primitive. Which agrees with the error message that is displayed in LV 8.5.

Just something for you all to be aware of.

Cheers & Beers

:thumbup: :beer:

[Aristos Queue]

QUOTE(Phil Duncan @ Jan 31 2008, 12:06 AM)

In LV 8.5 you CAN wire an array of classes to the flatten to XML primitive.

Grrrrr... that shouldn't have been enabled. My apologies for your wild goose chase. Such functionality is forthcoming, but was not ready for the 8.5 release.

[crelf]

QUOTE(Aristos Queue @ Jan 31 2008, 01:46 AM)

Such functionality is forthcoming, but was not ready for the 8.5 release.

Looking forward to it! :thumbup: