Skip to main content

UKOUG Day 4

The last day of the conference already...

The day started with a presentation on Datamodelling using JDev. The presenter showed how JDev could replace Designer for modelling. Imho JDev doesn't support logical modelling at all (he misused Java class models to represent a logical model), there is no repository and no relation between a logical and physical model. For just physical modelling JDev is fine, because all 11g database options are included. This modelling option will become available in SQL Dev also....

''After that I went to see my esteemed colleague Peter Lorentzen's talk on How to make your APEX Application Secure. He stated that APEX is secure, but developers make it unsecure. Nice statement Peter! One of his (many) good advices was not to use XE for an APEX (open) production environment as XE is not patched and you will be vulnerable to all kinds of attacks. He also showed a script attack by adding a small "Hello World" script as a value for a database varchar2 column - if you don't check the input and escape the output more dangerous scripts can be executed than just a small pop up box saying Hello. Even with Pete Finnigan on the front row making him kinda nervous, Peter did a good job!

My last session of the day - and the conference - was a two hour Masterclass on ADF by Duncan Mills. He showed us how all the XML files in JDev are created, what the connection was between all these XML files and how to tweak it. For instance how to change (as an example : change the backgroud color) the drag and drop feature in the faces_creator_configuration file. Great session, although he couldn't get through all his 72 (!) slides and tons of examples - have to buy the book (as I didn't win the signed copy).

After that the trip home. Doug Burns made the waiting at the airport more pleasant (and/or the Guinness) , but it still was a long trip. Thanks for the organisation for this great event, I hope to get back next year!
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. …