in the Integration Server, I have a publishable document type (I’ll call it “MainDoc”) that is associated with a connection of type “Universal Messaging” (UM) and has the encoding type “Protocol buffers”. MainDoc has a field of type “Document Reference”. I’ll call the referenced document type “SubDoc”.
SubDoc is not publishable. It was generated from an XSD and contains very many fields that are deeply nested. Some are document references themselves, others are defined inline.
node.ndf file for the MainDoc, there is the property
protoBufDescriptor which describes the document structure for the purpose of communication with UM. I decompiled this value (using com.google.protobuf.DescriptorProtos.FileDescriptorSet#parseFrom) and dumped the result to the console.
Thus I noticed that:
- The message type for MainDoc has a field “SubDoc” of type “TYPE_MESSAGE”
- There is a message type “SubDoc”
- The definition of the message type “SubDoc” contains no fields
How can it happen that the definition of “SubDoc” is empty? I’d expect that the protobuf definition contains a complete definition of MainDoc, including all its subdocs and their fields.
MainDoc works well, can be published and received in the IS, the data is transported correctly etc. But where is the protobuf definition for SubDoc??? (Actually, there are three fields in MainDoc whose definition is empty.)
Thank you for any hints.