Community
Participate
Working Groups
Needs 339905 Support for optional arguments requires changes to schema and WSDL generation to include choice/optional elements. Also, the current implementation of o.e.p.platform.database.oracle.publisher .sqlrefl.SqlReflector returns 'weird' results when argument defaults are used for a Stored Procedure (sets internal variable that distort 'overload' cases).
Created attachment 211346 [details] Proposed fix.
Created attachment 211347 [details] Supporting test cases.
The fix provides support for optional scalar, PL/SQL scalar, VArray, Object and ObjectTable arguments.
Optional attribute in generated service xml: <query> <name>OptionalArgTest4</name> <parameter optional="true"> <name>X</name> <type>ns1:dbws_phonetype_tableType</type> </parameter> <result> <type>xsd:string</type> <simple-xml-format/> </result> </query>
Snippet from generated WSDL showing minOccurs for optional argument 'X': <xsd:complexType name="OptionalArgTest4RequestType"> <xsd:sequence> <xsd:element minOccurs="0" name="X" type="ns1:dbws_phonetype_tableType"/> </xsd:sequence> </xsd:complexType>
Reviewed by: michael.norman@oracle.com Tests: all unit tests pass as expected; optionalarguments/OptionalArgumentTestSuite Revision: 10886
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink