Shredding and Querying with Oracle Offline Persistence in JET by Andrejus Baranovskis


I think offline functionality topic should become a trend in the future. Its great that Oracle already provides solution for offline – Oracle Offline Persistence toolkit. This is my second post related to offline support, read previous post – Oracle Offline Persistence Toolkit – Simple GET Response Example with JET. I have tested and explained with sample app how it works to handle simple GET response offline. While today I would like to go one step further and check how to filter offline data – shredding and querying offline.

Sample app is fetching a list of employees – Get Employees button. It shows online/offline status – see icon in top right corner. We are online and GET response was cached by persistence toolkit:

We can test offline behaviour easily – this can be done through Chrome Developer Tools – turn on Offline mode. Btw, take a look into Initiator field for GET request – it comes from Oracle Offline Persistence toolkit. As I mention it in my previous post – once persistence toolkit is enabled, all REST calls are going through toolkit, this is how it is able to cache response data: Read the complete article here.

Developer Partner Community

For regular information become a member in the WebLogic Partner Community please visit: ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Forum Wiki

Technorati Tags: PaaS,Cloud,Middleware Update,WebLogic, WebLogic Community,Oracle,OPN,Jürgen Kress

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.