HTTP Query String

Question

We use mod_plsql to create webpages. One annoying charactersitic of this framework is having to explicitly define all Query String parameters that a procedure could possibly accept.
We have some jquery stuff we're developing that retrieves data from oracle using PL/SQL procedures over http (mostly XML formated, but we're also lookg at JSON). We have 1 tool we're exavluating that does this, but fails, and we don't know why...I think it's because it is sending some query string parameters that are undocumented and we're not getting any notice to what might be missing/sent.
So, my question is, is there a way to tell what query string parameters are being passed to a procedure? Assuming it is failing by sending undefined parameters of course...

Answer 1

oBean wrote:
We use mod_plsql to create webpages. One annoying charactersitic of this framework is having to explicitly define all Query String parameters that a procedure could possibly accept.Why not use the 2 parameter call interface instead?
You add an exclamation mark to the URL call to the procedure. E.g.
instead of
http://my-server.mydomain.com/orcl/scott.myproc?name=John&code=123
the call is changed to the following:
http://my-server.mydomain.com/orcl/!scott.myproc?name=John&code=123
This instructs mod_plsql to pass the query string as name-value arrays. The signature of procedure SCOTT.MyProc will thus no longer look like this
create or replace procedure MyProc( name vachar2, code number ) is ...
But as follows:
create or replace procedure MyProc( name_array owa_util.vc_arr, value_array owa_util.vc_arr ) is
The procedure can now deal with variable query strings from the web browser.