Well, once a year we think that XDTO is a great mechanism for synchronization. Every time we stuck with some problems.
We are tying to create some XML objects which are configuration independent. We know about XDTOSerialization mechanism, we use it, but we are not very happy with it so we decided to try abstract XDTO objects.
To create initial schema we exported a smaller configuration scheme and the imported it back as a XDTOpackage with the following namespace: "". So it not directly related to configuration scheme and has another URI.
Then we export some objects. I will show only the most important parts
Code
Schema = XDTOFactory.ExportXMLSchema("http://abaco.com.ec/exchange/bodegamovil");
Factory = New XDTOFactory(Schema);
// For object types we directly create XDTO type and then Object
XDTOType = XDTOFactory.Type("http://abaco.com.ec/exchange/bodegamovil", TypeString);
XDTOObj = XDTOFactory.Create(XDTOType);
// For references we directly assign the required type
XDTOType = XDTOFactory.Type("http://abaco.com.ec/exchange/bodegamovil", TypeString);
XDTOObj = XDTOFactory.Create(XDTOType, String(Value.UUID()));
To set a reference for a new object, you can use the SetNewObjectRef method of the object and to create a reference by UUID, you can use the GetRef method of the manager of that object type:
There is no way to read XML using XDTO without second parameter? What is the point of XDTO and definitions then if I have to define everything manually?! I need XDTOSerialization mechanism for non-platform types.
Alexey, if you need to serialize and deserialize infobase objects automatically, you can use the XDTO serializer. Here is an example for JSON, but the same you can use for XML: .
But will it work for custom objects (not from configuration)? The problem is that I have different objects in configurations, so I need intermediate object (just for exchange) with some attributes and I have rules in both configuration to convert exchange object to configuration object. That is why I have hopes for XDTO.
We have been using XDTOSerializer for importing configuration objects and it is no go for different configurations. if I add just one parameter to one configuration (or the user wants to add) it will require changes to another configuration although new field could be just additional comment which does not make sense to synchronize to mobile.
I think XDTO ReadXML should understand the type of objects it is reading. In my example XML file clearly defines via "xmlns" field and its name what object it is. I can not use your suggestion #5 because simply I do not know which object is next. So by reading its type I could suggest further actions. I could implement this behavior by reading raw XML, but it is a lot of extra code which seems unnecessary.
Also I have found several publication (on Inforstart) which claim that automatic type suggestion should work, but there are no clear example how to make it work.
Alexey, in case of using custom objects, you need to define them in the Configuration tree: Common/XDTO packages. And then in the source application you can add web services, that use those packages and in the target one you need to add WS-references to your web services.
Timofey, they are defined in the configuration tree. In Common/XDTO packages. Please look again at the configuration I have sent you. There is no problem with Web services / exchanging information. The only problem is that the platform does not recognize types of XDTO objects read from XML.
Please modify the configuration I have sent you to read at least one XDTO object from XML using XDTO Refernce, XML Schema or XDTO Data Model (I really don't care which one to use) but WITHOUT defining object type in code like you suggested in #5. It should be possible. All the information needed is provided in XML and Schema (or XDTO reference).
Please help me with this one. If you say that is impossible I'll be forced to write low-level XML parser to basically implement logical XDTO behavior.
I have reviewed the example you suggest. There is no code in this example which shows how to write / read to/from XML. I can not omit writing to XML because it is used in standard changes registration mechanism.
Also it seems to me that an example is not very good. It transmit one big XDTO object with hierarchy (root item). This could provoke out of memory if you transfer a greater sized catalog.
Do you have a valid XML schema for your data? XDTO needs a description of data to read the format. In your example there was only data. That is why gave a link to an example with XDTO packages.
Here I made a simple example on how to make serialization of configuration objects into XML and reading them back. You can use XDTOSerializer object and if the types that you use present in XDTO packages (built in or added by you), then your objects will be written and read without need to specify types.
Please see the attached infobase dump.
Code
&AtServerNoContext
Function ExportXMLAtServer()
XMLWriter = New XMLWriter;
XMLWriter.SetString("UTF-8");
XMLWriter.WriteXMLDeclaration();
XMLWriter.WriteStartElement("v8msg:Message");
XMLWriter.WriteNamespaceMapping("v8msg", "http://v8.1c.ru/messages");
XMLWriter.WriteStartElement("v8msg:Body");
Query = New Query;
Query.Text =
"SELECT
| SalesOrder.Ref
|FROM
| Document.SalesOrder AS SalesOrder";
QueryResult = Query.Execute();
SelectionDetailRecords = QueryResult.Select();
While SelectionDetailRecords.Next() Do
Object = SelectionDetailRecords.Ref.GetObject();
XDTOSerializer.WriteXML(XMLWriter, Object, XMLTypeAssignment.Explicit);
EndDo;
XMLWriter.WriteEndElement();
XMLWriter.WriteEndElement();
Return XMLWriter.Close();
EndFunction
&AtServerNoContext
Procedure ImportXMLAtServer(XML)
XMLReader = New XMLReader;
XMLReader.SetString(XML);
XMLReader.Read();
Data = XDTOFactory.ReadXML(XMLReader);
For Each XDTODocument In Data.Body.DocumentObject_SalesOrder Do
Document = XDTOSerializer.ReadXDTO(XDTODocument);
Object = Undefined;
If Document.Ref.IsEmpty() Then
Object = Documents.SalesOrder.CreateDocument();
Else
Object = Document.Ref.GetObject();
EndIf;
FillPropertyValues(Object, Document);
Object.Write();
EndDo;
EndProcedure
Desktop version