Issue 7744: Section 1.2.8.5 (wsdlcorba-rtf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: In the example: <portType name="Example.SomeInterface"> <operation name="bar" parameterOrder="_target pi"> <input message="tns:Example.SomeInterface.bar"/> <output message="tns:Example.SomeInterface.barResponse"/> <fault message="_exception.Example.BadRecord"/> <fault message="_exception.Example.UnknownError"/> <fault message=”tns:CORBA.SystemException”/> </operation> </portType> Most of the WSDL2java tool will use element'name' as a parameter's name. So, on receiving the WSDL as above (page 1-25), most WSDL2java tool will report an error in process for mapping WSDL to java. Proposed solution: Maybe we should add a 'name' attribute in the fault element. For example, consider the following IDL: module Example{ exception BadRecord{ String why; }; Interface SomeInterface{ Long bar(in float pi) raises(BadRecord),UnknownError } } It should be mapped to: <portType name="example.SomeInterface"> <operation name="bar" > <input message="tns:Example.SomeInterface.bar" /> <output message="tns:Example.SomeInterface.barResonse"/> <fault message="_exception.Wxample.BadRecord" name="badRecord"/> <fault message="_exception.Example.UnknownError" name="error"/> <fault message="tns:CORBA.SystemException" name="systemError"/> </operation> </portType> Resolution: : Accept proposed change from source Revised Text: In section 1.2.8.5: On page 1-26, Change: " <fault message="_exception.Example.BadRecord"/> <fault message="_exception.Example.UnknownError"/> <fault message="tns:CORBA.SystemException"/> " to: <fault message="_exception.Example.BadRecord" name="Example.BadRecord"/> <fault message="_exception.Example.UnknownError" name="Example.UnknownError"/> <fault message="corba:CORBA.SystemException name="CORBA.SystemException"/> " On pages 1-20, 1-21 (twice), 1-22 (twice), 1-23, and 1-24 (twice), of section 1.2.8.2 Change: " <fault message="tns:CORBA.SystemException"/> " to: " <fault message="corba:CORBA.SystemException" name="CORBA.SystemException" /> " Actions taken: September 13, 2004: received issue March 10, 2005: closed issue Discussion: WSDL 1.1 states the following: " 2.4.5 Names of Elements within an Operation The name attribute of the input and output elements provides a unique name among all input and output elements within the enclosing port type. In order to avoid having to name each input and output element within an operation, WSDL provides some default values based on the operation name. If the name attribute is not specified on a one-way or notification message, it defaults to the name of the operation. If the name attribute is not specified on the input or output messages of a request-response or solicit-response operation, the name defaults to the name of the operation with "Request"/"Solicit" or "Response" appended, respectively. Each fault element must be named to allow a binding to specify the concrete format of the fault message. The name of the fault element is unique within the set of faults defined for the operation. " Thus, to obey wsdl we have to accept the proposed change. Also, all messages in the example operation definition need to be namespace qualified End of Annotations:===== te: Tue, 14 Sep 2004 01:20:18 +0800 (CST) From: =?gb2312?q?bin=20zhou?= Subject: new issues reporting - number 1 To: issues@omg.org Hi,there We are OMG Uni. member (Member ID: 45687). We have found a issue/bug for the 'CORBA to WSDL/SOAP Interworking Specification' (03-11-02). Posted below. ---------------------------------------------------------- Name: Bin Zhou Company: National Lab. on Distributed Processing mailFrom: http://cn.f153.mail.yahoo.com/ym/Compose?To=hncszhoubin@yahoo.com.cn Specification: CORBA to WSDL/SOAP Interworking Specification Section 1.2.8.5 In the example: Most of the WSDL2java tool will use element'name' as a parameter's name. So, on receiving the WSDL as above (page 1-25), most WSDL2java tool will report an error in process for mapping WSDL to java. Proposed solution: Maybe we should add a 'name' attribute in the fault element. For example, consider the following IDL: module Example{ exception BadRecord{ String why; }; Interface SomeInterface{ Long bar(in float pi) raises(BadRecord),UnknownError } } It should be mapped to: ------------------------------------------------------------- best regards, Bin -------------------------------------------------------------------------------- Do You Yahoo!? 150万曲MP3疯狂搜，带您闯入音乐殿堂 美女明星应有尽有，搜遍美图、艳图和酷图 Date: Thu, 23 Sep 2004 13:10:02 -0400 From: Tom Rutt Reply-To: tom@coastin.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en To: wsdlcorba-rtf@omg.org CC: "Vinoski, Stephen" , "Moore, Keith" , iwasa , Masahiko Narita Subject: Discussion for Issue 7744, need name attribute for Fault messages in operations The proposed resolution from the source for Issue 7744 is attached. It proposes adding name attributes to the fault messages in the wsdl operations mapped from IDL inferfaces. WSDL 1.1 states the following: " 2.4.5 Names of Elements within an Operation The name attribute of the input and output elements provides a unique name among all input and output elements within the enclosing port type. In order to avoid having to name each input and output element within an operation, WSDL provides some default values based on the operation name. If the name attribute is not specified on a one-way or notification message, it defaults to the name of the operation. If the name attribute is not specified on the input or output messages of a request-response or solicit-response operation, the name defaults to the name of the operation with "Request"/"Solicit" or "Response" appended, respectively. Each fault element must be named to allow a binding to specify the concrete format of the fault message. The name of the fault element is unique within the set of faults defined for the operation. " Thus, to obey wsdl we have to accept the proposed change for Issue 7744 below: What do you all think about this required change to the corba to wsdl spec? Tom Rutt WSDL to corba and corba to wsdl rtf chair ---- Issue 7744: Section 1.2.8.5 (wsdlcorba-rtf) Click here for this issue's archive. Source: National Lab, Distributed Process, China (Dr. Bin Zhou, hncszhoubin@yahoo.com.cn) Nature: Uncategorized Issue Severity: Summary: In the example: Most of the WSDL2java tool will use element'name' as a parameter's name. So, on receiving the WSDL as above (page 1-25), most WSDL2java tool will report an error in process for mapping WSDL to java. Proposed solution: Maybe we should add a 'name' attribute in the fault element. For example, consider the following IDL: module Example{ exception BadRecord{ String why; }; Interface SomeInterface{ Long bar(in float pi) raises(BadRecord),UnknownError } } It should be mapped to: ------- Tom Rutt WSDL corba rtf chair -- ---------------------------------------------------- Tom Rutt email: tom@coastin.com; trutt@us.fujitsu.com Tel: +1 732 801 5744 Fax: +1 732 774 5133 1G就是1000兆，雅虎电邮自助扩容age="_exception.Example.BadRecord"/> . to: . On pages 1-20, 1-21 (twice), 1-22 (twice), 1-23, and 1-24 (twice), of section 1.2.8.2 Change: . . to: . . -- ---------------------------------------------------- Tom Rutt email: tom@coastin.com; trutt@us.fujitsu.com Tel: +1 732 801 5744 Fax: +1 732 774 5133