Skip to main content

OOW2006 - Day 2 (Tuesday) : Developer Day

Image
By
On this Tuesday I spent the whole day at the Hilton (only 1,5 block from our hotel) attending sessions from the Developer track. The day started of with the Developer keynote of the day : Tom Kyte with Things you think you know. The message was that things (read "Oracle software") changes over time and with every Oracle update your knowledge needs an update too. The quote of the day :
      "It ain't so much the things we don't know that get us into trouble.
      It's the things you know
      that just ain't so or
      just ain’t so anymore or
      just ain’t always so."
This great presentation (especially if it's presented by the master himself) is also downloadable from asktom. You can get an impression by watching the first 3 minutes on video from Eddy Awad's site.

The second session of the day was Oracle BPEL Process Manager Performance and High Availability by Francis Ip and Randy Stafford. This was the only session at OOW where I misjudged my knowledge (obviously I didn't read the abstract quite well): I got lost after 15 minutes and took the time to finish my notes from the previous day.

After that I went to Business Rules : Core to Agile Applications by Manoj Das. He explained the goals and working of Business Rules a new part of the SOA Suite - rules can be integrated in a BPEL process. The statement was that, because (some) business rules are not static, but dynamic, you need an easy way to change the rules (by the end user). Business Rules is Oracle's solution to that. You should use BR only for rules that are volatile, like discount percentages, client categorization (e.g. gold, silver or bronze customers) etc. He showed some screen prints of the tool, alas no live demo. The IT savings of using a business rule engine is estimated by Gartner on 5 up to 40%, so it looks quite promising - when the product is mature.

The next thing was a Hands-on-Lab Oracle ESB Synchronization. In this session we were challenged to create an end-to-end solution using ESB. A nice break: doing something yourself instead of listening....

The last session of the day was CERN: Building Real-World Solutions with Oracle Application Express by Giovanni Chierico. At CERN (the inventors of the internet!), APEX is used for developing small database centric applications for users all over the world. They managed to put as many as 10 applications in production in 1 year. He showed some screen shots that looked really nice and ended with giving some tips to the audience.

After that I headed over to the Blogger meetup, where I met around 10 of my fellow bloggers. Very good to meet the people you read! A couple of us broke up halfway the meeting to take a bus (one of the 250!) to the Cow Palace to watch the Elton John show. Arriving there I was astonished by the quantity and quality of the food and drinks (even when we arrived quite late). The show of Elton and Devo was great - sadly I had to miss Joan Jett. I went back rather early and had just to wait 10 minutes for a bus (in contrast to some colleagues who had to wait over an hour).

Comments

Post a Comment

Popular posts from this blog

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 old Employ
1 comment
Read more

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

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