It has been a very lean and easy option of .Net to able serialize/deserialize any serializable object instance.
Only closest option in Delphi is to stream the component using WriteComponent/WriteComponentRes of TStream/TWriter (used for Form storage as DFM, for example). It can be then read back using appropriate counterpart ReadComponent/ReadComponentRes.
Depend on your situation, simply calling .Assign method would work if you are coping data from one instance to another. But it only works between inherited classed which know about each other.
Can we find there something which will allow to pass objects states in more readable format?
There is a very powerful infrastructure available to do full serialization without knowing underlying class structure – RTTI (Run-time Type Information).
All functions we would be looking at are defined in TypInfo.pas unit.
First thing first. To be able to work within RTTI, you need to operate on the object which has published and public properties.
function GetPropList(TypeInfo: PTypeInfo; out APropList: PPropList): integer;
A function will return number and reference to the list (array) of properties published (public and published) by the class (VMT information). List will also include published methods. Simply walking through it will give you an access to property/method information.
In our example we are not interested in the published methods, so lets filter it out:
var i: integer; lPropInfo: PPropInfo; lPropCount: integer; lPropList: PPropList; lPropType: PPTypeInfo; begin lPropCount := GetPropList(PTypeInfo(AObject.ClassInfo), lPropList); for i := 0 to lPropCount - 1 do begin lPropInfo := lPropList^[i]; lPropType := lPropInfo^.PropType; if lPropType^.Kind = tkMethod then Continue; // ... processing of the properties ... end; end;
What other Kind of information is present in the list? Bellow is full definition of the type
type TTypeKind = (tkUnknown, tkInteger, tkChar, tkEnumeration, tkFloat, tkString, tkSet, tkClass, tkMethod, tkWChar, tkLString, tkWString, tkVariant, tkArray, tkRecord, tkInterface, tkInt64, tkDynArray);
Now you are ready to get or set the value of the property:
function GetPropValue(Instance: TObject; const PropName: string; PreferStrings: Boolean = True): Variant;
procedure SetPropValue(Instance: TObject; const PropName: string; const Value: Variant);
And now you are ready to serialize your object, store it, load definition and deserialize an object back. And it could be not necessarily the same object.
You would have to loop through the properties, read the values, and store it as an XML for later use.
I am not going to go through all specific details in this post, instead, you can find a full code for XML Class serializer here.
20 Comments
Serguei Dosyukov · Mar 1, 2009 at 17:58
A new version has been uploaded to the website
Only unprocessed properties are set when deserializing an object, preventing double processing mentioned by stoxx.
Dorin · Mar 2, 2009 at 12:01
Hm… just a short review of source, it seems, doesn’t work with references, am I right?
Serguei Dosyukov · Mar 2, 2009 at 12:31
What do you mean? References to external object instances?
Under StorageOptions, enable soIncludeObjectLinks.
Stefan · Jun 30, 2009 at 10:03
Hi,
i try to read a serialized TCollection descendant, but i dont dont work for me.
The code stops in the following line:
if IsPublishedProp(aPropertyInstance, lPropName) and Assigned(lPropInfo^.SetProc) then
lPropInfo.SetProc is nil for the Count-Property (because its a read-only property!).
Any suggestions?
Stefan
Serguei Dosyukov · Jun 30, 2009 at 10:25
Stefan,
You cannot deserialize read-only properties
Do you have a sample which would demonstrate the problem?
Stefan · Jun 30, 2009 at 10:35
hi
i got the following classes:
which i serialize with the following code:
This works fine! I get a xml-file in a format which i excpect.
If i try to read this object back from the xml-file it just dont work:
Greets,
Stefan
Serguei Dosyukov · Jun 30, 2009 at 11:12
this kind of class property definition is not supported
You need to modify it as following
Luca · Jul 23, 2009 at 05:11
Hello,
Very nice component, congratulations.
It seems to work only with published (not public) properties, so arrays are not supported, am I right?
You need some fixes to work with Delphi 2009, e.g. in functions SaveToFile and LoadFromFile you have to switch to AnsiString.
Regards,
Luca
TObjectList : SaveToStream und LoadfromStream - Delphi-PRAXiS · Jan 3, 2013 at 03:10
[…] […]
Eigene Objekte via tcp versenden - Delphi-PRAXiS · Apr 17, 2014 at 00:28
[…] […]