I just obtained Apex Listener 2.0, and was hoping to use its RESTful features on an instance that does NOT have Apex 4.x installed (in fact, it has Apex 3.2.x but the APEX_PUBLIC_USER account is locked)
While I've been able to get APEX Listener 2.0's ordinary PL/SQL gateway feature working in the absence of a functioning APEX, (e.g.: http://host:port/apex/path/schema.package.procedure?param1=val1¶m2=val2 returns what is expected.)
I haven't been able to get the RESTful feature functioning. I am not surprised, since it is certainly not documented to work without APEX.
I just wanted to confirm this with others.
Although I did manually edit the <db_name>al.xml and <dbname>_rt.xml files, setting the db.username to something else, a request generates the following error:
Dec 28, 2012 1:08:53 PM oracle.dbtools.common.config.db.DatabasePoolConfig readPoolConfig
WARNING: The pool_config view or table was not found in schema: MY_SCHEMA
Also, it looks like:
java -jar apex.war help
does NOT show any way that resource templates for restful services can be configured. They only can be configured through the web interface. I suspect this is because the information in the resource templates is saved not in the web application itself, but in Oracle meta-data tables. Is that right?
you are right: RESTful services via APEX Listener 2.0 depend on APEX 4.1 (with patch 13815223) or APEX 4.2 (with corresponding configuration, as documented in the [url http://docs.oracle.com/cd/E37097_01/doc/install.42/e35123/otn_install.htm#BABFGHFJ]APEX 4.2 Installation Guide). Indeed, the configuration information for RESTful services is not only entered, but also stored within APEX.
If you want to use RESTful services without APEX, you can use the previous APEX Listener release 1.1, which had a small bdb-database to store that configuration. But obviously, you'll lose advantages (and official support, some day) when using an outdated release.