This content has been marked as final. Show 5 replies
We are considering this for a futire release.
You shouldn't want to reference "orawsv" at all. This is way to easy to Google... At current it is very easy to find all the APEX or (old) Oracle application servers (/plsql/), Oracle Portal etc, out there anyway. If you like to try some hacking attempt on another persons environment, then there is a lot of demo ground out there.
Edited by: Marco Gralike on Feb 25, 2013 8:42 PM
You can modify the servlet mapping to use a more restrictive URL pattern that can only target the WS for PL/SQL :
If we try to use the Query WS, we'll get an error, but accessing PL/SQL procs will be OK.
BEGIN DBMS_XDB.deleteServletMapping('orawsv'); DBMS_XDB.addServletMapping('/orawsv/DBSCHEMA/*', 'orawsv'); END; /
Currently you can/should probably use Apache reverse proxy to create that functionality or have a look at Oracle Enterprise Gateway: http://www.oracle.com/us/products/middleware/soa/enterprise-gateway/overview/index.html
thank you kindly ....