Comments on: Notifying ADF applications of database changes – fast and lean using Database Query Result Change Notification – Part One Friends of Oracle and Java Wed, 24 Jun 2015 09:59:44 +0000 hourly 1 By: tarekfathi2003k Wed, 21 May 2014 08:18:23 +0000 Hi
The invokeAction is deprecated in 12c. What is the alternative for invokeAction.

By: zinon Tue, 20 Nov 2012 08:19:52 +0000 Hi Lucas,

I am trying to develop a system which notifies the application according to modification in database like your sample.I m using JDeveloper version and Oracle Database 11g Enterprise Edition(remote). I have followed the instructions, downloaded the demo application (step1) edited db configurations, created the DB_NOTIFICATIONS table and the trigger on EMP table
The trigger works and adds rows to DB_NOTIFICATIONS about the modifications. I also added the CHANGE NOTIFICATION privilege to my current user.
When I execute the project with Employees.jspx It registers the listeners to DB. There is 2 logs on the console screen:

– Register for table DB_NOTIFICATIONS select id, event_context from db_notifications where event_type=’EMP_DML’
– HR.DB_NOTIFICATIONS is part of the registration.

and I can see the data of EMP table and data of its on the browser. When I made a modification on EMP table (changing sal value as in the example)
The trigger adds a row to DB_NOTIFICATION table. But it does not reach to onDatabaseChangeNotification() method to handle the modification in the middle tier.

The query registration process is being passed
without any exception. The only problem is DB does not notify the application over jdbc. I am running the application
on my local weblogic server. Only the DB is remote.

I have created a thread in oracle forums about this sample maybe you look at.

I do not understand why it does not work. Do you have any idea about the problem?


By: Lucas Jellema Thu, 28 Jun 2012 13:11:16 +0000 Hi Hal,

Connecting to JMS from the database seems at first like something fairly trivial. Unfortunately, on closer inspection, it is not trivial at all.

Publishing however from the database to JMS is easy enough: you can expose AQ as a JMS queue on WebLogic and from ADF you can register on that JMS queue. That gives a fairly straightforward route from database to ADF application as well. The question remains what and when to publish on AQ – what is the ‘notification trigger’.
This article has some information: The suggestion however of using Java Stored Procedure to call out JMS turned out to be non-trivial, so I suggest you stick with AQ based approach.

kind regards,


By: luc Mon, 18 Jun 2012 19:24:38 +0000 Hi Lucas. Great post, especially because you use the db_notifications table to register and push database changes. Much cleaner then registering all queries on by one in the ADF Application as I was doing. Curious about part II

By: Hal Mon, 18 Jun 2012 10:29:39 +0000 Did you ever tried connecting JMS from Oracle database to ADF? We’ll must to do in a development something similar to this article, and we were thinking on using JMS.