Hello,
We are trying to upgrade our ORDS stack to the latest version 24.3 from the version 19.4 (I know a bit old but very stable).
Our current issue is to have the equivalent of urls mapping which are radically changed (among others) on the latest version.
Let me explain the current situation:
We have many database pool with one ORDS instance and want to never expose the schema in the url, for those requirement we currently use, in 19.4, the url-mapping.xml like:
<?xml version="1.0" encoding="UTF-8"?>
<pool-config xmlns="http://xmlns.oracle.com/apex/pool-config">
<pool name="a" base-path="/path-a" schema-name="APP" updated="2020-03-17T07:24:22.354Z"/>
<pool name="b" base-path="/paht-b" schema-name="APP" updated="2020-03-17T07:24:22.354Z"/>
</pool-config>
This allow us to consume/expose our api like:
/ords/path-a/my-resource/:id => use database a with shema APP
/ords/path-b/my-resource/:id => use database b with shema APP
Now on latest version, handling multiple database is a bit different but path request mapping still existing using the paths file:
https://docs.oracle.com/en/database/oracle/oracle-rest-data-services/24.3/ordig/configuring-additional-databases.html#GUID-370709D3-146D-4B69-B16C-8BA54174F5CA
But the result requires to put the schema in the url:
/ords/path-a/app/my-resource/:id
/ords/path-b/app/my-resource/:id
I'm afraid that default schema name is no more natively possible with the latest version of ORDS or I've missed something.
Is there any way to reproduce the same behavior as before which is to have a default schema to avoid to have/expose it in the url ?
Thank you for your support