The behavior of the store operation when a null object body is provided must be defined in the requirements.
Please notice that these requirements should be affected:
3.4.6.2.7 The fifth part of the request shall contain the list of objects to store.
3.4.6.2.8 The fourth and fifth list must be the same size as there is only entry in each for
each object to be stored. If they differ in size and INVALID error is returned with the extra
error information integer giving the index of the list entry without a matching entry in the
other list.
3.4.6.2.12 The type of the body of the object should be checked against the declared type in
the relevant service specification, if different an INVALID error is raised.
The behavior of the store operation when a null object body is provided must be defined in the requirements.
Please notice that these requirements should be affected: 3.4.6.2.7 The fifth part of the request shall contain the list of objects to store. 3.4.6.2.8 The fourth and fifth list must be the same size as there is only entry in each for each object to be stored. If they differ in size and INVALID error is returned with the extra error information integer giving the index of the list entry without a matching entry in the other list. 3.4.6.2.12 The type of the body of the object should be checked against the declared type in the relevant service specification, if different an INVALID error is raised.