Skip to main content

Earplugged, Blindfolded and Jetlagged

After a long long journey I finally made it to my hotel next to San Francisco Airport. I can see the planes as they come and go, but luckily can't hear them.
The first leg of my trip, from Amsterdam to Cincinnatti, wasn't that bad: I had a complete row of three chairs for myself! Delta provided everyone with earplugs and blindfolds, so I stretched my legs and took some naps (still don't know if it is a good idea to take as much sleep as you can on a flight or to try to stay awake as long as you can, in order to survive a none hour time lap). The offerings on the entertainment system where good enough and even the food was ok.
I had less then two hours to change planes in Cincinnatti, and - with the experiences of the Sam Francisco and Houston Immigration lines - I wasn't certain that that would be enough. To my big suprise there was no line at all (I don't want to call three people in fron of me a 'line')! I even had to wait at the luggage belt before my suitcase arrived.
The second leg was worse. The airplane was completely booked, and there were lots of children aboard. I don't have anything against children (I have two of my own), but they don't make me happy when they're sitting right behind me and play around with the table tray and kick against the chair every time I almost fall asleep.
And also the service for this part was very minimal: no inflight entertainmant, only food for purchase and too few beverages. But what can you expect when you go for the cheapest option (only 450 euro ($600,-) for the complete trip).
In my hotel I stayed awake until 9:30 and then fell in a deep sleep. From which I woke up at... 3 AM! With some effort I managed to stay in bed, with some little naps, until 6. After breakfast I'll go to the car rental to get my car and drive the scenic route to ... Monterey!
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…

Consuming a REST Web Service returning JSON in APEX

In APEX you can define a web service that returns XML as below - all declarative, just a few steps through a wizard.


Then generate a report on top of that web service - again just a few clicks through a wizard. The generated query looks like this:
select xtab."customerName"      , xtab."customerId"   from apex_collections c,            XMLTable('/Response/S_getCustomerListTableArray/S_getCustomerListArrayItem' passing xmltype001             COLUMNS "customerName" PATH 'customerName'                   , "customerId"   PATH 'customerId'           ) xtab  where c.collection_name = 'CUSTOMERLIST'
So the result of the web service is stored in an XMLTYPE column. And it's easy to spot where you're definitions for the Response XPath and Output Parameters are used.
But what if your web service returns JSON - as more and more web services will do so? If you switch the Output Format of the web service definition to JSON, th…