How to make Database Actions (SQL Developer Web) to see missed function parameters?

_Dima_

PL/SQL function was created:

CREATE OR REPLACE FUNCTION TOTAL

(

   number1 IN NUMBER,

   number2 IN NUMBER

) RETURN NUMBER AS

BEGIN

   RETURN number1 + number2;

END TOTAL;

Above function was RESTful-enabled:

DECLARE

   PRAGMA AUTONOMOUS_TRANSACTION;

BEGIN

   ORDS.ENABLE_OBJECT(p_enabled => TRUE,

                      p_schema => 'BOB_USR',

                      p_object => 'TOTAL',

                      p_object_type => 'FUNCTION',

                      p_object_alias => 'total',

                      p_auto_rest_auth => FALSE);

   COMMIT;

END;

Database Actions shows that created total function doesn't have parameters but actually it has 2 parameters.

How to make Database Actions to see missed 2 function parameters?

kdario

This is a bug which is already described here:

https://community.oracle.com/tech/developers/discussion/4498138/ords-pl-sql-autorest-incomplete-openapi-def#latest

If you need this info just to see how to invoke your web service, pass input parameters as json payload in request body, for example:

{
"number1": 10,
"number2": 20
}

If you need correct Open API definition for documentation purposes, you will have to edit this generated definition in Swagger editor and add missing parts.

Or you can expose plsql function manually (template+handler) instead of AutoREST (this approach also has some issues described in mentioned forum thread, but at least you will get input parameters in Open API definition :) ).

_Dima_

Database Actions generated above CURL code. What correct code should look like for a function with 2 parameters?

kdario

This is a bug which is already described here:

https://community.oracle.com/tech/developers/discussion/4498138/ords-pl-sql-autorest-incomplete-openapi-def#latest

If you need this info just to see how to invoke your web service, pass input parameters as json payload in request body, for example:

{
"number1": 10,
"number2": 20
}

If you need correct Open API definition for documentation purposes, you will have to edit this generated definition in Swagger editor and add missing parts.

Or you can expose plsql function manually (template+handler) instead of AutoREST (this approach also has some issues described in mentioned forum thread, but at least you will get input parameters in Open API definition :) ).