CORBA26 — padding at the end of a non-fragmented 1.2 request message

Suppose a GIOP 1.2 request message is sent for an operation with no
argument. In this case the request body is empty because there is no
argument.

Furthermore, the whole request message is non-fragmented, i.e. the
2nd least significant bit of Flags in the request header is 0. Now if the
request message header ends on a boundary which is not 8-byte
aligned. Should the request message be extended with extra padding after the
request message header to make the whole request message multiple of 8?

I think the relevant statement is in section 15.4.1 (page 15-31):

"For GIOP version 1.2, if the second least significant bit of Flags is 1,
the sum the message_size value and 12 must be evenly divisible by 8"

My intepretation of the statement is that the condition I just described
does not meet this critera. Hence the message should not be padded to
multiple of 8. It should just be ended with the end of the message header,
just like previous GIOP versions.

I'm asking for clarification on this issue because I'm seeing a different
behaviour in another ORB implementation and would like to pre-empt any
interoperability problem in future.

see above