Skip to main content

OOW 2009 : Wednesday

I started off with a good breakfast with my roomies Marco and Jacco. Because there wasn't any interesting session in the first timeslot (or I couldn't find it), I attended the Exhibition Hall - which is mainly the same as previous years. Everyone wants to 'scan your badge' so they can spam you afterwards.
Next there were two sessions I really liked, and - it may or may not be a coincidence - both were 30 minutes 'power sessions'. The first one was by Mark Drake, the Product Manager for XML DB, about Managing XML Content with APEX. Very good job, although having live demo's obviously are a risk...and that's why I like them!
The next one was about Row Level Security / VPD and APEX. The presenter had a good demo and explained the stuff nicely.
I followed the keynote from the OTN Lounge (it is less boring with a beer). It wasn't a surprise anymore that The Governator would attend. Arnold emphasized that technology will deliver the solution for CO2 reduction - he didn't say that technology was also the cause of all kinds of pollution...
Larry's story - the only presentation from Oracle without the safe harbor slide - didn't contain anything astonishing new: Oracle has Linux and VM (that's a three year old story); has an Exadata machine thats an (undefined) number of times faster than the one form IBM (Sunday's news..); My Oracle Support will get better; Fusion Apps are on their way (with demo).
The last real session of the day was Building a Mashup with APEX. The presenter painted out an architecture where you create webservices on your database objects, and consume those in APEX on XE. The reasons for doing so was that
- you don't need a license for XE (that's true, but you do need a license for the underlying database, so that's a non-argument)
- he thought that APEX itself would have a negative impact on the performance of his database (which is obviously also a non-argument, as APEX adds only a very little bit of overhead - and creating extra layers as he suggested will create more overhead)
- the DBA's didn't like the idea for having an 'application in the database': the database is for data, not for applications... (An misconception that some old school DBA's hang on to).

And at night : The Appreciation Event with Aerosmith. And they rocked - especially when you know that Steven Tyler (the leadsinger) is 61!
1 comment

Popular posts from this blog

Showing a success message after closing a modal dialog

APEX 5 comes with Modal Dialogs out of the box. Very neat. Especially for adding and changing data. And to minimise the number of time a user has to click, it could be useful to add a "Close Dialog" process after the actual data processing. When the data processing fails, the Dialog stays on top showing the error. When data processing runs fine, the Dialog is closed ... without any confirmation. And this might be scary for a shaky user.

So how can we provide the user some feedback? On Page 4 of the Sample Dialog Application you can see one solution: up on a Dialog Closed Event on the parent page it does a redirect to refresh the parent page appending the success message of the "Close Dialog" process. This has two drawbacks. First, it probably refreshes more than necessary. And second, if you're using multiple layers of dialogs (dialogs that open other dialogs) the message appears in the "parent dialog".
As an alternative you could follow these steps: 1…

APEX 5 New Static File Features

In APEX 4 you could upload files - like CSS files, JavaScript files, Images and whatever else you like - into the APEX Repository. When you navigate to Shared Components, there is a Files section that offers three different options:
CSS Files are always uploaded (and changed !) for the whole Workspace. For Images and Static Files (usually JavaScript) you could choose whether they should be available for the whole Workspace or for a specific Application only. And if you had a lot of files - e.g. a lot of images - then you had to go through the upload process one-by-one. But that's usually a one time only thing. If you make changes to the CSS and JavaScript files - and that's a continuous process in development - then you had to delete the existing file and upload the new one. Over and over again. And meanwhile fighting the cache of the webserver and your browser.  And another irritating issue: You couldn't use relative references in your CSS or JavaScript files as they just…

Using LDAP for Authentication and Authorization within APEX

One of my current customers would like to use their LDAP (Microsoft Active Directory) server for authentication and authorization of APEX applications. Of course we tried to set up a standard LDAP Authenication that's available within APEX. But we couldn't get that to work. Maybe it has to do with the fact that the client stored their Users within Groups within Groups within .... . Or maybe it doesn't do a full tree walk in the directory. Or maybe it is just because it is Microsoft - and not Oracle Internet Directory (OID). So we moved to a custom Authentication using the DBMS_LDAP functions (and some examples from the Pro Oracle Application Express book and Tim Hall - a.k.a. Oracle Base).

One of the issues we encountered that we wanted to use the user's login name, like "jdoe" and not his full name ("John Doe"). And the login name is stored in the "sAMAccountName" attribute. But authenticating using just "jdoe" didn't work. …