Skip to main content

UKOUG Day 4

Image
By
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!

Comments

Post a Comment

Popular posts from this blog

apex_application.g_f0x array processing in Oracle 12

By
If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one: then you disable the " Escape special characters " property and the result is an updatable multirecord form. That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for ...
Post a Comment
Read more

Filtering in the APEX Interactive Grid

By
Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good o...
1 comment
Read more

Stop using validations for checking constraints !

By
 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function ...
Post a Comment
Read more