Issue 18152: Missing PolicyValue encoding instructions (corba-rtf) Source: (, ) Nature: Revision Severity: Significant Summary: Section 17.3.1 of CORBA 3.1 / 3.2 says: 17.3.1 Structures PolicyValue This structure contains the value corresponding to a Policy of the PolicyType indicated by its ptype. This representation allows the compact transmission of QoS policies within IORs and Service Contexts. **The format of pvalue for each type is given in the specification of that Policy.** When the ZIOP 1.0 specification describes the ZIOP policies, it does not give the format for pvalue. Resolution: Revised Text: Actions taken: October 10, 2012: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 10 Oct 2012 06:32:52 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Duncan Grisby Employer: mailFrom: duncan@grisby.org Terms_Agreement: I agree Specification: ZIOP Section: 7.4.3 FormalNumber: formal/2010-02-05 Version: 1.0 Doc_Year: 2010 Doc_Month: February Doc_Day: 01 Page: 9 Title: Missing PolicyValue encoding instructions Nature: Revision Severity: Minor CODE: 3TMw8 B1: Report Issue Description: Section 17.3.1 of CORBA 3.1 / 3.2 says: 17.3.1 Structures PolicyValue This structure contains the value corresponding to a Policy of the PolicyType indicated by its ptype. This representation allows the compact transmission of QoS policies within IORs and Service Contexts. **The format of pvalue for each type is given in the specification of that Policy.** When the ZIOP 1.0 specification describes the ZIOP policies, it does not give the format for pvalue. X-Virus-Scanned: by XS4ALL Virus Scanner Date: Fri, 12 Oct 2012 10:25:41 +0200 From: Johnny Willemsen Reply-To: jwillemsen@remedy.nl Organization: Remedy IT User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120825 Thunderbird/15.0 To: Duncan Grisby , "corba-rtf@omg.org" Subject: Re: Fwd: Re: issue 18152 -- ZIOP xTF issue Hi, Do you mean in an encapsulation, or just bare? All the other messaging policies defined in section 17.2 require a CDR encapsulation for the pvalue. > The challenge with it being bare is that it can be unclear what byte order to use. What would happen if you have a big-endian GIOP message that contains a messaging QoS service context whose encapsulated Messaging::PolicyValueSeq is little-endian? If pvalue is not itself an encapsulation, what should the endianness of the marshalled value be? It has to be in a cdr encapsulation Regards, Johnny Regards, Duncan. On Wed, 2012-10-10 at 20:25 +0200, Johnny Willemsen wrote: Thanks for reporting this. This has been an oversight and wasn't aware of that reference in the corba spec. The idea (and our implementation) is that we just marshal the attribute as part of a specific ZIOP policy into the pvalue. When you get the TAO source code check TAO/tao/ZIOP/ZIOP_Service_Context_Handler.cpp Regards, Johnny On 10/10/2012 06:56 PM, Juergen Boldt wrote: From: webmaster@omg.org Date: 10 Oct 2012 06:32:52 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Duncan Grisby Employer: mailFrom: duncan@grisby.org Terms_Agreement: I agree Specification: ZIOP Section: 7.4.3 FormalNumber: formal/2010-02-05 Version: 1.0 Doc_Year: 2010 Doc_Month: February Doc_Day: 01 Page: 9 Title: Missing PolicyValue encoding instructions Nature: Revision Severity: Minor CODE: 3TMw8 B1: Report Issue Description: Section 17.3.1 of CORBA 3.1 / 3.2 says: 17.3.1 Structures PolicyValue This structure contains the value corresponding to a Policy of the PolicyType indicated by its ptype. This representation allows the compact transmission of QoS policies within IORs and Service Contexts. **The format of pvalue for each type is given in the specification of that Policy.** When the ZIOP 1.0 specification describes the ZIOP policies, it does not give the format for pvalue. Juergen Boldt Director, Member Services 140 Kendrick Street, Building A Suite 300 Needham, MA 02494 USA Tel: 781 444 0404 x 132 fax: 781 444 0320 www.omg.org []