Skip to main content

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

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

Comments

Post a Comment

Popular posts from this blog

How to create neatly formatted Excel documents using PL/SQL?

By
If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...
21 comments
Read more

Refresh selected row(s) in an Interactive Grid

By
In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...
Post a Comment
Read more

APEX ReadOnly Pages - The easy way

By
If your Oracle APEX Application requires different types of access - full access or readonly - for different types of users, you can specify a Read Only Condition on Page level (or Region, Item, Button, etc.).  You can set an Authorization Scheme on Application level, so it'll be applied to all pages. So if you have an Authorization Scheme named 'User Can Access Page' defined by a PL/SQL function like this: return apex_authorization.user_can_access_page ( p_app_id  => :APP_ID , p_page_id => :APP_PAGE_ID , p_user    => :APP_USER );  then you can code all the logic in the database using the APEX Repository, your own tables or a combination to define whether a user has access to that page or not. But alas it is not possible to define something similar Application wide for a Read Only condition. You can specify an Authorization Scheme 'User has Read Only Access' using a similar signature as the one above and use that on each and e...
Post a Comment
Read more