ADF 12cR2: Using WebSockets for warning Task Flow Concurrency

Hi all,

I started to upload ADF 12cR2 POCs in my GITHub Repository with samples I develop for my current clients for technical feasibility.

https://github.com/DanielMerchan/adf

The first project is WebSocketConcurrentTaskFlowEdit.

Basically, it uses CDI Managed Bean + Jakarta EE WebSockets for communicating users which are concurrently editing the same information in an ADF Page / ADF Bounded Task Flow.
 

The components are the following:
  • TaskFlowWebSocketServer.java: Contains the WebSocket Server Side Logic.

  • TaskFlowSessionHandler.java: It is a CDI Bean injected in our TaskFlowWebSocketServer.java for decoupling the logic and handling the mapping between Socket Sessions with Task Flows.

  • TaskFlowWebSocket.js: It is the WebSocket Client written in JavaScript which is the responsible of opening the Socket Connection and manage the messages received (in JSON Format) from the TaskFlowWebSocketServer.java

  • SocketHandler.java: Is an ADF Managed Bean used by TaskFlowWebSocket.js for sending a message to the backend to produce a JSF Faces Message based on the message received in the socket. This component is optional as also we can intercept the message and use directly JS to show the notification using ADF Components or just plain HTML/CSS non-obstructive popup.

  • test.jsf: It is the test page which initializes the WebSocket connection when pageLoad by passing the userId and the TaskFlowId from the binding layer.

  • Fake-tf.xml: It is just a mock Task Flow for demo purposes.

As you can see, I have used CDI Managed Beans, Injection and easy annotations for developing my WebSocket Server Endpoint.

Have a look into the code and execute test.jsf. Login in one browser with user A and another browser with user B.

You will see the warning ;).

Happy learning!. Follow your dreams. 

Comments

Post a Comment

Popular posts from this blog

OJET: Inter-Module communication in TypeScript Template

Image
In this post I bring another example on how to Communicate Modules using the Oracle JET - TypeScript Template based on the Oracle JET Cookbook: InterModule Communication From now and so on will create multiple examples using TypeScript for those who are not familiar with it and wants to turn the Cookbook examples into TypeScript :). The example ( ojet-typescript-list-detail ) can be found as usual in my GitHub repository: https://github.com/DanielMerchan/ojet-examples This example is a bit different compared to the Cookbook example where the modules are not running at the same time within a Module. This example is built as described in the following images: Customers module acts as the Wrapper Module. It coordinates when to load the list and detail modules. Customers module makes use also of signals npm module for communication between Customers-List, Customers-Detail. Explanation of the Example customers.js is the coordinator responsible module for: initiali
Read more

OJET: Build and Deploy in an Application Server

Image
There are some other sources where an Oracle JET Application is packaged and deployed as a WAR in Oracle WebLogic Application Server (Arda Eralp) https://blogs.oracle.com/ardaeralp/deploy-oracle-jet-application-to-weblogic-server (Andrejus Baranovski's) http://andrejusb.blogspot.com/2016/07/serving-oracle-jet-application-from.html They may look bit old or maybe because they call directly grunt tasks by using the grunt-cli . In this post I will update a bit these posts in Oracle JET 6.1.0 and the usage of ojet build (instead of calling the grunt tasks) for also building the corresponding WAR file. The example can be found in my GIT repository: https://github.com/DanielMerchan/ojet-examples Let's start... Install grunt-war module in your Oracle JET Application. npm install grunt-war --save-dev Create a war.js (or call it whatever you want) in /scripts/grunt/config folder under your souce files. This is a sample code inside of it, check https://www.npmjs.com/packag
Read more

OJET: Select All options using only Checkboxset

Image
This is an example on how to select all other options by using another oj-checkboxset. GitHub: ojet-checkbockset-select-all The idea is to keep track of the selection and make use of the on-value-changed as described in the following code. self.colorOptions = ko.observableArray([ { id: "blueopt", value: "blue", color: "Blue" }, { id: "greenopt", value: "green", color: "Green" }, { id: "redopt", value: "red", color: "Red" }, { id: "limeopt", value: "lime", color: "Lime" }, { id: "aquaopt", value: "aqua", color: "Aqua" }, ]); self.selectAll = ko.observableArray([]); self.currentColor = ko.observableArray(["red"]); self.selectAllOptionChanged = (event) => { const newSelection = event.detail.value; if (newSelection.indexOf('all')
Read more