Skip to main content

APEX Plugin Directory

For all you APEX Plugin developers: There is already an operational APEX Plugin Directory available at You can add your own Plugins there and view and download the ones your co-APEX developers came up with.
Looks pretty slick, with just one drawback: It is not built in APEX (at this moment).
Oracle also has one under construction at


Buzz Killington said…
I've already seen no less than like 5 different bloggers setting up various sites, groups, google things for plugins.

Personally it should really just be handled through Oracle sort of how Apple handles the App Store or how jquery indexes plugins. Not as rigid for submission, but if you want an app, you go one place. Everyone makes sure the most up-to-date plugin is on Oracle's site, and then everyone is happy.

What I think will inevitably happen is you'll get a graveyard of sites that started out storing all these plugins, but people will get other jobs, or whatever and will never update the sites. So you'll get outdated plugins and that doesn't help anyone.

Just look at what happened with the slew of wikis, blogs and sourceforge projects...etc - haven't been updated in years. This it the fate of disparate plugin registries too.

That's just my 2 cents anyway.
Johannes said…
Though I think is a fantastic initiative I'm afraid I have to agree with Buzz.

Personally however I feel that it won’t be a bad idea if Oracle would let a 3rd party "manage" the plug-ins, something like what IBM did with Eclipse. Creativity works best for developers if they feel that their efforts are “managed” by an independent party.

I do however feel that the plug-ins that are Oracle “certified” should be clearly indicated.


Popular posts from this blog

apex_application.g_f0x array processing in Oracle 12

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 processing y…

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 …