Details
-
Bug
-
Status: Resolved
-
Resolution: Done
-
unspecified
-
None
-
None
-
Operating System: All
Platform: All
-
5858
Description
It seems like the OCP plugin will only be able to parse OCP messages correctly when the OCP agent produces those messages in a way that each pair of terminal start and end elements is followed by a line feed. Take the hello indication message for instance, a successful hello would look like the following:
<msg xmlns="http://uri.etsi.org/ori/002-2/v4.1.1">
<header>
<msgType>IND</msgType>
<msgUID>0</msgUID>
</header>
<body>
<helloInd>
<version>4.1.1</version>
<vendorId>MTI</vendorId>
<serialNumber>101-12</serialNumber>
</helloInd>
</body>
</msg>
Obviously, this does not make sense as a normal XML document typically does not contain line feed characters. The OCP plugin must be able to process OCP messages in "normal" XML format in addition to the above mentioned ones. A normal OCP message should look like the following:
<msg xmlns="http://uri.etsi.org/ori/002-2/v4.1.1"><header><msgType>IND</msgType><msgUID>0</msgUID></header><body><helloInd><version>4.1.1</version><vendorId>foxconn</vendorId><serialNumber>123</serialNumber></helloInd></body></msg>
