Skip to main content


The (rather ambitious) schedule for today was :

Lost in JDeveloper by Sten Vesterli : Sten guided the (Forms experienced) audience in creating an ADF Swing Client App ofcourse declaratively (next to AJAX this is the buzzword of the conference : everything should be declarative, you can be a programmer when you' re able in controlling your mouse ;-) ).
Programming Real Applications with APEX by Andrew Woodward : Again everything declarative but now using APEX instead of JDev. The point was: you can create simple applications faster than using Oracle Forms but when you need more advanced features you'll need to program Javascript and AJAX. But that's only temporarily, because in the next version(s) you also will be able to create AJAX components declaratively.

Modelling on the cheap by Andrew Clarke (I chaired this one) : Andrew sketched out the pros and cons of different modelling tools - from whiteboards to (free) datamodelling tools. As far as he knows the best free datamodelling tool on the market today is Schemester.

Oracle SQL Developer Advanced Features by Sue Harper : Sue pointed out how to make our own extensions - as extra tabs and right-mouse-options - on SQL Dev and demonstrated the power of the Migration Workbench. Also APEX content in your database is visible throug SQL Dev and a nice new feature (in the next version) will be to possibility to view trace files as a very flexible TKProf like output!

Oracle Forms Roundtable by Grant Ronald : In this round table all attendees could present their views on Oracle Forms and what features should be added in subsequent releases. Alas not much came out - I think we are so "comfortable" with the imperfections of Form... Grant suggested a couple of enhancements like a kind of JTable option (where you can click on the header for automated sorting etc) and a new look-and-feel / color scheme. Ofcourse no fixed promises where made...

Integration of BI Publisher and APEX by Dimitri Gielis : Dimitri, enthousiastic as ever, showed the possibilities of using BI Publisher for creating very good looking reports. The integration between the two products is very good. But a great disadvantage is that BI Publisher is not as free-of-charge as APEX is (maybe this is Oracle's way to earn some money out of APEX - apart from the database licenses?).

Special : Trevor Baylis - a World Famous British Inventor : Trevor, a 72 years old 'world famous' inventor (I never heard about him, but he is the inventor of, amongst a lot of other stuff, the wind-up radio - now I understand why we've got one from the organisation) presented his views on " invention". In his opinion you can learn to invent and, just like there is a School of Arts, there also should be a School of Inventions. The presentation was very amusing.

Event Dinner : One hall was transformed into a ' Christmas Eve' kind of room and we all enjoyed the drinks, food and (more or less) the DJ...
Post a 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. …