Issue 5790: CORBA-WSDL/SOAP: Section 1.2.7.10 (corbawsdl-ftf) Source: Fujitsu (Mr. Tom Rutt, tom@coastin.com) Nature: Uncategorized Issue Severity: Summary: Section 1.2.7.10 ­ Only public state members are mapped. Since use of the Dynamic Any api allows access to both the private and public members, this restriction was challenged by the AB reviewer as unwarranted. Also the sentence "For example, DII/DSI bridges will be unable to process value types." is not justified. The dynamic ANY api can be used to access value type state members in a DII/DSI based gateway. If private state cannot be represented, an input value type parameter which has private state will not be mapped to the IDL server. Proposed Solution: Delete offending sentence about dynamic gateways. Unless the private member restriction can be justified, change the spec to map both private and public value type state members. Resolution: Remove the restriction of not mapping Private state members Revised Text: Remove the restriction of not mapping Private state members. Revised Text: In 1.2.7.10: Remove the following text from the first sentence: “, though only public attributes are mapped.” Change: “ Basic valuetypes are mapped to structs, as noted above. Private fields are ignored. For example, consider the following: // IDL valuetype sampleX { public short a; private long b; } The private field “b” is ignored, so this maps to: <complexType name="sampleX"> <xsd:sequence> <xsd:element name="a" type="xsd:short"maxOccurs="1" minOccurs="1"/> </xsd:sequence> “ to the following: “ Basic valuetypes are mapped to structs, as noted above. Both Public and Private fields are mapped. For example, consider the following: // IDL valuetype sampleX { public short a; private long b; } This maps to: <complexType name="sampleX"> <xsd:sequence> <xsd:element name="a" type="xsd:short"maxOccurs="1" minOccurs="1"/> <xsd:element name="b" type="xsd:int"maxOccurs="1" minOccurs="1"/> </xsd:sequence> Actions taken: December 18, 2002: received issue November 6, 2003: closed issue Discussion: Since the dynamic ANY api can be used to access all value type state members in a DII/DSI gateway, the restriction to not mapping private state members needs to be removed End of Annotations:===== Date: Tue, 17 Dec 2002 12:30:41 -0500 From: Tom Rutt Reply-To: tom@coastin.com X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en To: juergen@omg.org, issues@omg.org, "corbawsdl-ftf@omg.org" Subject: MARS and AB FTF issues for CORBA-WSDL/SOAP interworking Juergen, could you please file these as official issues for the FTF to resolve. Thank you: Tom Rutt corbawsdl FTF chair --------------------- Initial FTF Issues on 02-10-12-draft-adopted-spec.PDF FTF Issue 5 Source: MARS PTF and AB review Only public state members are mapped. Since use of the Dynamic Any api allows access to both the private and public members, this restriction was challenged by the AB reviewer as unwarranted. Also the sentence "For example, DII/DSI bridges will be unable to process value types." is not justified. The dynamic ANY api can be used to access value type state members in a DII/DSI based gateway. If private state cannot be represented, an input value type parameter which has private state will not be mapped to the IDL server. Proposed Solution: Delete offending sentence about dynamic gateways. Unless the private member restriction can be justified, change the spec to map both private and public value type state members Section 1.2.7.10 Date: Tue, 18 Mar 2003 20:23:56 -0500 From: Tom Rutt Reply-To: tom@coastin.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en To: "corbawsdl-ftf@omg.org" Subject: ISSUE 5790 proposal X-OriginalArrivalTime: 19 Mar 2003 01:26:58.0750 (UTC) FILETIME=[A2980DE0:01C2EDB6] Issue 5790: CORBA-WSDL/SOAP: Section 1.2.7.10 (corbawsdl-ftf) Click here for this issue's archive. Source: Fujitsu (Mr. Tom Rutt, tom@coastin.com) Nature: Uncategorized Issue Severity: Summary: Section 1.2.7.10 - Only public state members are mapped. Since use of the Dynamic Any api allows access to both the private and public members, this restriction was challenged by the AB revieweras unwarranted. Also the sentence "For example, DII/DSI bridges will be unable to process value types." is not justified. The dynamic ANY api can be used to access value type state members in a DII/DSI based gateway. If private state cannot be represented, an input value type parameter which has private state will not be mapped to the IDL server. Proposed Solution: Delete offending sentence about dynamic gateways. Unless the private member restriction can be justified, change the spec to map both private and public value type state members. Discussion: Since the dynamic ANY api can be used to access all value type state members in a DII/DSI gateway, the restriction to not mapping private state members needs to be removed. Proposed Resolution: Remove the restriction of not mapping Private state members. Proposed Revised Text: In 1.2.7.10: Remove the following text from the first sentence: Change: Basic valuetypes are mapped to structs, as noted above. Private fields are ignored. For example, consider the following: // IDL valuetype sampleX { public short a; private long b; } The private fiel d is ignored, so this maps to: to the following: Basic valuetypes are mapped to structs, as noted above. Both Public and Private fields are mapped. For example, consider the following: // IDL valuetype sampleX { public short a; private long b; } This maps to: Actions taken: December 18, 2002: received issue -- ---------------------------------------------------- Tom Rutt email: tom@coastin.com; trutt@fsw.fujitsu.com Tel: +1 732 801 5744 Fax: +1 732 774 5133