Skip to main content

OOW2008 - Sunday

Due to the jet lag this Sunday had a very early start. I was wide awake at 5:oo AM, so I had a long time to check my e-mail, take a shower and eat a full American breakfast. After registering for the conference it took about 5 minutes to walk into someone I know...it's a small world after all.
For me the conference started with a Hands-on-Lab : Extending the APEX Framework with Web 2.0. To me there where just a few new features mentioned in the handbook, but I guess most people didn't finish all examples within an hour. The handbook will be available as an OBE within a couple of weeks. The next session was on Achieving ROI with Oracle Database 11g and APEX. It was about a new application Harvard Pilgrim needed to offer health insurance to individuals. Instead of taking 1000's of phone calls, they decided they needed an on line self service application - and built it in APEX. Another good example how you can build an application with APEX in less than a month. You can find the application here.
After that Joel Kallman presented on Globalization with APEX. Apart from Java (with resource bundles) and .Net (using resource files), in APEX you can do the translation after the development. It needs just 6 easy steps: Map, Seed, Export (to XLIFF), Translate, Import/Apply and Publish. The translated versions of an application are replica's from the original one (with their own application id). You can only make changes to the original application. After changes you just have to make the additional translations and (re)publish the translated one. Live has never been so easy. One free tip from Joel : Create your database using the AL32UTF8 character set, so you can easily handle all languages... Examples of multi language APEX applications are BioQuebec and ProMed. He also announced some new APEX 4.0 features, but I will collect all those features for a separate post.
After the session about Weird PL/SQL by Steven Feuerstein and the - funny political - keynote by Carville and Matalin I went to the Blogger meetup. Allways good to match names and faces...
Post a Comment

Popular posts from this blog

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid. The use case I'll cover right here is probably more common - and therefore more useful!

Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user.The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even worse) while you…

Dockerize your APEX development environment

Nowadays Docker is everywhere. It is one of the main components of Continuous Integration / Continuous Development environments. That alone indicates Docker has to be seen more as a Software Delivery Platform than as a replacement of a virtual machine.

However ...

If you are running an Oracle database using Docker on your local machine to develop some APEX application, you will probably not move that container is a whole to test and production environments. Because in that case you would not only deliver a new APEX application to the production environment - which is a good thing - but also overwrite the data in production with the data from your development environment. And that won't make your users very excited.
So in this set up you will be using Docker as a replacement of a Virtual Machine and not as a Delivery Platform.
And that's exactly the way Martin is using it as he described in this recent blog post. It is an ideal way to get up and running with an Oracle database …

Using multiple Authentication Schemes for your APEX application

Recently someone asked me how he could implement multiple authentication schemes for his APEX application. He would like to use (some kind of) Single Sign-on authentication and - as an alternative - an Application Express Authentication. The problem is ... you can only define one Authentication Scheme being "Current" for an application! So how can we solve this issue?

First, we need te be aware that multiple applications can share their authentication by using the same cookie. Thus if you specify "MYCOOKIE" as the Cookie Name in Application A as well as in Application B, you can switch from A to B and back without the need of logging in again. It doesn't matter what Authentication Scheme Type you are using!

Knowing this, we are halfway our solution. We need two Applications. One - the "real" application - using the Application Express Authentication, let's name this one "LAUNCHPAD". And another one using the Single Sign-on Authentication…