Skip to main content

OOW2010 Wednesday

Alas I missed the Benelux cocktail part last night, because the dinner took somewhat longer than expected. The dinner was extremely good though.
This day started with a session by John Scott Spendolini about "Recovering from APEX mistakes" - I didn't know they existed but nevertheless. Good session on how to undo changes you've made, debugging etc. The next one was by Marco Gralike on XML-DB (what else could it be?). Good, detailed info with some nice examples. Not all demos worked like he meant to, but that's the price you pay when you mess with them the night before! Especially the event firing mechanism when you drop a file in an XML folder are very cool! Marco, we definitely need those for our ODTUG presentation!
Then Raj did a presentation on collections, enthusiastic and dynamic us usual. But also his deno didn't turn out as expected. The best take away from this session was the idea to create views on top of your collections, so you can maintain the code more easy.
Larry's Wednesday's keynote was rather disappointing. No new announcements, just a recap of the things announced earlier this week. And that took rather long, so I missed the Fusion Apps demo as I headed for a session on EBR by Boeing. They already really use it in their mission critical business applications. By implementing EBR they managed to reduce the outage for an application upgrade from 9 hours to less then 1! Very impressive.
Next was the Blogger Meetup. Always a good opportunity to match faces with names. And the. Off to the Appreciation event! It was definitely more crowded than last year, with long lines for the food. And some good bands too! Don Henley may look somewhat older, but his voice still sounds like 30 years ago. And the Black Eyed Peas surprised me, with a very good show. This is the first time I saw the whole crowded joining the band: All yo part people in da house, say yoo-hoo.
I got a bus back around 12, because I need a relative good night sleep for my session tomorrow. I am curious how many people will show up, as I heard a lot of people saying they'll leave on Thursday....
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…

A review of APEX World 2017 - Day 1

Last week the SS Rotterdam was the beautiful location of the largest gathering of APEX Developers worldwide. With around 380 (!) attendees a new high was set. And they came from all over the world : I spotted people from The Netherlands, Belgium, Switzerland, Austria, Croatia, Germany, Denmark, Norway, UK, Ireland and the USA. And I even might have missed one or two ….

The event started with a presentation by the “father of APEX”, Mike Hichwa, talking about "Oracle APEX Past, Present and Future”. Of course everyone is curious what the APEX future might bring: Friendly URL’s, automated testing, more JSON, concurrent APEX versions, third party Oauth 2 authentication (think Facebook, Google), APEX app diff and more, a lot more, REST capabilities. And now we have to wait for APEX 5.2 … and that might take a while! 
After this keynote, the conference split up in three tracks. After the coffee break I returned to to big theatre where Geertjan Wielenga talked about "Finally Javas…

Push changed rows to an Interactive Grid

For pushing changes from the database to the end user, the regular solution is using websockets. A change in a record is detected - using a trigger or using the CQN (Change Query Notification) feature - and a notification is send to a websocket server. That websocket server broadcasts the notification over a channel to all browsers that are tuned in to that websocket channel. Then the browser reacts to that notification, usually showing an alert or refreshing a report. This trick is described on multiple sites, just Google for "oracle apex websockets" or similar.

So back in the old days, we used that notification in the browser to refresh the (interactive) report. But along comes the Interactive Grid (IG). While he full-refresh mechanism still works for IG, an IG has also the option to refresh just one row.  So wouldn't it be awesome that just the changed row(s) get refreshed upon a change in the database, instead of the whole report? Can we do it ... yes we can!
First i…