| commit | 54e1875fa42491b5afdd395fb515418479a4a1ad | |
| author | Adenilson Cavalcanti <adenilson.silva@indt.org.br> | |
| Mon, 13 Oct 2008 19:29:31 +0000 (13 15:29 -0400) | ||
| committer | Adenilson Cavalcanti <adenilson.silva@indt.org.br> | |
| Mon, 13 Oct 2008 19:29:31 +0000 (13 15:29 -0400) | ||
| tree | bc068a8b90a15619f61af87a0740a6904f724d4e | treesnapshot (tar.gz zip) |
| parent | 88d78f266587560b499f7e094ca2f5832059a559 | commitdiff |
Reverting that hack of creating osync_data_change direct from ram XML data.
I discovered the reason why osync_xmlformat_parse was failing: it expected
a xmlformat-data-doc just like I informed in the gc_initialize.
But I started to think that maybe the problem was that I was using a
OSyncXMLFormat object (binary) to create the OSyncData that was supplied
to OSyncChange.
I reverted to xmlformat-data and it is working now.
I discovered the reason why osync_xmlformat_parse was failing: it expected
a xmlformat-data-doc just like I informed in the gc_initialize.
But I started to think that maybe the problem was that I was using a
OSyncXMLFormat object (binary) to create the OSyncData that was supplied
to OSyncChange.
I reverted to xmlformat-data and it is working now.
| src/gcalendar.c | diffblobblamehistory |