Somebody can help here please?
If ename is the parameter, then the URL should be /employees?ename=v
my URI-Muster look like so /store/per/:value
When i pass value it works fine. But when i pass value to "v" i have that error.
It seem like ORDS reject v as Parameter
That's an Apex error, not ords.
Can you show us your handler code?
There is nothing in my Code about APEX. The error come from ORDS. The Code is a Productive Code. I can not show it here
so is the
PROCEDURE store (
p_ename OUT VARCHAR2,
p_message OUT VARCHAR2,
p_value IN VARCHAR2
v.value = p_value;
I call in the the Ords like so and Source_typ is PL/Sql
p_message => message,
My URI-MUSTER look like so /store/per/:value
when i give a Value 1 or 2 or 3 it works fine. When i give v1, v2, v3 works fine too. But when i give v it doest not works and i have that error
No idea, for example I have the following URI attached to this POST Handler code
owa_util.status_line (200, '', false);
OWA_UTIL.MIME_HEADER ('text/plain', TRUE);
curl -X POST \
-H 'cache-control: no-cache' \
-H 'postman-token: 3eb15ff4-86f1-c6b4-b3c0-312b9803a6cb'
then I get my 'v' parameter printed nicely back in HTML as expected
My case is a GET handle with PL/SQl as source Type. I have made a test for POST and it works fine for me too. It doest not works for GET.
With get i have java.sql.SQLException: ORA-20001: Path=V rejected
You can't have a GET for PL/SQL, it HAS to be POST
I meant to say POST can only be PLSQL...
hmmm, I do not agree with that. shows the screenshot I always use GET for PL / SQL because I hide my logic in the pl / SQL package and I'm flexible with that. and it always works for me.
I think that is a bug java.sql.SQLException: ORA-20001: Path=V rejected
Yeah, your're right, i'm wrong....POSTS can only be PL/SQL - my brain 'thought' too fast
Ok thanks you. But why?
you've enabled the OWA plsql gateway and you're trying to do ORDS/REST