Kris Rice

Using a HTTP GET, the passing of variable is quite simple.  All that is needed is to make the URI Template include them.  I this example "myget?a={a}&b={b}"  The values of a and b are converted into a bind variable for use in the sql statement. With this Resource Template definition, the results are $ curl  "https://apex.oraclecorp.com/pls/apex/raptor/test/myget?a=hello&b=bye" {"items":[{"

 For people trying out the database service on http://cloud.oracle.com, data loading got 1 step easier.  Before this, there would would have to be an APEX user created with roles granted.  While this still will work, now you can simple use the cloud user created at signs ups.  This is the administer's login created in the initial welcome emails. To setup a new user in the cloud that

There's a 2 ways to lockdown which applications/URLS are accessible for any APEX installation with the APEX Listener. First, I showed the new javascript method in the 2nd half of this post.  This is very nice as it stops any database communication at all. Now let's talk about the PL/SQL validation function and the part that I forgot to document.  The normal  PL/SQL Validation that has been in

OTN is putting on a set of labs on Monday before the show that are FREE to anyone.  You can join David Peake from the Application Express team, Jeff Smith from the SQL Dev team, Maria Colgan from the Optimizer, and myself for the labs. There's 2 rooms that will be running with the below agenda.  The first room is performance/optimizer focused.  Starting with Maria and the optimize then showing

The Oracle APEX Listener 2.0 is officially out. There's a TON of changes in this release. The first how you get it up and running. For the standalone version, it's very simple to be up and running quickly. Simply type "java -jar apex.war" and follow the prompts. This will get you up and running.  The biggest changes are in the REST services and I'll blog more on that later. The command line