Skip to main content

OOW2006 - Day 0 (Sunday) : The Opening Ceremony

For me OOW started on Sunday morning with the ODTUG Oracle Developer Suite Special Interest Group Meeting in the Hilton. In this session 2 Oracle Emps of the Forms and Designer Development Depts answered questions of the audience.

The highlights :
  • The main goals for Forms 11 are : better Application Server integration; higher interoperability (with webservices, BPEL and browser); ease of upgrade.

  • JInitiator will be replaced by (native) JVM

  • WebUtil will be a part of Forms (not a seperate utility anymore)

  • Forms PL/SQL scanner that checks the quality of the code

  • No plans for extra UI widgets

  • Oracle Applications is migrating to Forms 10gR2, so Forms is here to stay

  • XML Publisher is the standard reporting tool in Applications (you can imagine the consequences for the future of Oracle Reports)

  • Designer 11 will not contain any new functionality, just a new version to keep up with Forms
Of course no time frame for the release has been given.

At 6:00 pm Charles Phillips had the honour of kicking of OOW with the Opening Keynote. Charles announced that the Oakland Arena will be renamed to Oracle Arena (according to the basket and ball, it had something to do with basketball....). After that Charles emphasized that all Applications (EBS, JD Edwards, Peoplesoft etc), will be supported and extended "unlimited", next to Fusion. Then he announced - and even live demo'ed! - Oracle Accelerate, a tool to simplify the setup for your Oracle Apps instance, just by answering a few questions.

At 7:00 the first party of OOW started: The Welcome Reception in the tents on Howard Street.
Post a Comment

Popular posts from this blog

Refresh selected row(s) in an Interactive Grid

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 worse) while you…

Dockerize your APEX development environment

Nowadays Docker is everywhere. It is one of the main components of Continuous Integration / Continuous Development environments. That alone indicates Docker has to be seen more as a Software Delivery Platform than as a replacement of a virtual machine.

However ...

If you are running an Oracle database using Docker on your local machine to develop some APEX application, you will probably not move that container is a whole to test and production environments. Because in that case you would not only deliver a new APEX application to the production environment - which is a good thing - but also overwrite the data in production with the data from your development environment. And that won't make your users very excited.
So in this set up you will be using Docker as a replacement of a Virtual Machine and not as a Delivery Platform.
And that's exactly the way Martin is using it as he described in this recent blog post. It is an ideal way to get up and running with an Oracle database …

Using multiple Authentication Schemes for your APEX application

Recently someone asked me how he could implement multiple authentication schemes for his APEX application. He would like to use (some kind of) Single Sign-on authentication and - as an alternative - an Application Express Authentication. The problem is ... you can only define one Authentication Scheme being "Current" for an application! So how can we solve this issue?

First, we need te be aware that multiple applications can share their authentication by using the same cookie. Thus if you specify "MYCOOKIE" as the Cookie Name in Application A as well as in Application B, you can switch from A to B and back without the need of logging in again. It doesn't matter what Authentication Scheme Type you are using!

Knowing this, we are halfway our solution. We need two Applications. One - the "real" application - using the Application Express Authentication, let's name this one "LAUNCHPAD". And another one using the Single Sign-on Authentication…