Skip to main content

OOW2006 - Day 4 (Thursday) : The Final, Closing Ceremony

Due to a pleasant evening on Wednesday, I had to skip the first session (at 8:00!). But at the start of the second session, Test-Driven Development in the World of PL/SQL by PL/SQL Evangelist Steven Feuerstein, I was quite awake. Steven demonstrated - in his own special interesting way : what a great presenter! - the advantages of Test Driven Development. The message: Specify your testcases and build your test program before you even start building the program-to-test!. He also announced and demonstrated Quest Code Tester, what looks like a great tool to support PL/SQL unit tests. I surely will try this out soon. Available for download at ToadWorld, free until the end of February.

After that one I went to Peter Koletzke for a session with the - rather long title Oracle JDeveloper 10g with Oracle ADF Faces and Oracle JHeadstart: Is it Oracle Forms Yet?. He pointed out the similarities and dissimilarities between Oracle Forms and JDeveloper - with and without JHeadstart. His conclusion was that Oracle Forms is still better than JDeveloper (because of the learning curve and the more interactive Forms UI), but JDeveloper with JHeadstart is way ahead of Forms - and the development is still going on! One of the funniest parts of his presentation was the moment that a cell phone rang very loud at the first row and he jumped up - dropping his microphone - stating that he would request a JDev enhancement for a ringtones option! Quote of the day: Whatever it is that hits the fan will not be evenly distributed.

The next session was Implementation of an End-to-End Application with Oracle SOA Suite by Roman Dobrik. A good overview presentation of the diverse SOA components, when to choose which component and how these components should co-operate.

The last session of this OOW was a very interesting Oracle BI Discoverer Futures: Protect, Extend, Integrate by Mike Durran. The presentation covers three aspects:
  • Protect : He made clear how Oracle sees the future of Discoverer: SE with new releases and functionality or EE to gain new functionality like integration with BI Publisher (aka XML Publisher), Dashboards and Delivers.
  • Extend : New functionality like Custom Members, Graph Styles and Portal Publishing
  • Integrate : With BI Publisher (he even showed a working demo of this one), Delivers - with Alerting and Distributing iBots that act on worksheets, like BPEL processes that are instantiated upon specific outcomes of worksheet data - and Dashboards. All very cool and promising features!


The last event was the closing ceremony/party, called It's a wrap!, with - again - lots of good food, drinks and music.
All in all it was a very interesting OOW and I really enjoyed it. Hopefully I'll be 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…

It's happening again ... running for the ODTUG Board of Directors 😉

For the third time in a row I'll be running for ODTUG's Board of Directors. But after ending as a runner up twice, I am sure I'm going to make it this time! But not without your help!

My campaign statement this year is:
I have been attending and presenting at Kscope conferences since 2007. This not only resulted in a vast amount of knowledge, but also - and even more important - a huge number of friends from all over the globe.  I want to see ODTUG grow and spread this community feeling even more! 
My experience as an attendee, presenter and content lead has provided the basic foundation to be a director. Next to that, my personality and (global) network will be beneficial to the whole board and organization. 
Since March I have served on the Board of Directors in a limited term for a Director who stepped down due to a career change. This has allowed me to have unique insight of all the things that are going on in and around the ODTUG organization. As the train was already ro…

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…