In previous blog How is OData request routed to Offline data store by OData offline plugin , according to comment, the Offline store will only be available once it is opened successfully. The open operation is done in Device native API, delegated in line 232.
The exec is available in exported module returned by require(‘cordova/exec’):
And now I would like to understand how this exec is delegated to Java Native API in Android platform.
In folder android I have found this cordova.js:
The exec call is implemented by module defined in cordova.js:
Here means the exec is implemented by androidExec:
Key logic of androidExec implementation
1. meaning of parameters success, fail, service, action, args
- service: Java class name
- action: Java class method name
<script> var String = window.jsinterface.getSomeString(); </script>
Back to implementation of AndroidExec:
var msgs = nativeApiProvider.get().exec(bridgeSecret, service, action, callbackId, argsJson);
it will again delegate the call to exec method of instance returned by nativeApiProvider.get().
Again look at implementation in nativeapiprovider.js, from the comment in line 21 we can know the currentApi returned by get comes from either ExposedJsApi.java or PromptBasedNativeAPI.
The ExposedJsApi.java could be found from this location:
It is a Java interface with method exec defined:
And the Java class SystemExposedJsApi implements the interface, delegates call to the instance of class CordovaBridge.
CordovaBridge will delegate to PluginManager:
Plugin manager first gets responsible plugin Java class by name, then perform the execute method of plugin.
For example this is OData offline plugin service class, in its execute method we can find there are lots of IF-ELSE branch to implement different offline operation.