OpenEdge Development: Mobile Applications - Product ...

Creating a JSDO for a Mobile resource
Creating a JSDO for a Mobile resource
The following code fragment shows a simple JavaScript coding sequence for creating
a JSDO, starting the attempted login of the user:
// create Session and set it for HTTP Basic Authentication
var pdsession = new progress.data.Session();
pdsession:authenticationModel = progress.data.Session.AUTH_TYPE_BASIC;
// log in, i.e., authenticate to the Mobile Web application
pdsession.login('/SportsMobile', username, password);
if pdsession.loginResult == progress.data.Session.LOGIN_SUCCESS {
}
// load catalog for a service that's part of the Mobile Web application
pdsession.addCatalog('/SportsMobile/static/mobile/SportsMobileSvc.json');
// create JSDO
var dsCustomer = new progress.data.JSDO({
name : 'dsCustomer',
autoFill : true,
events : {
'afterFill' :
[ {
scope : this,
fn : function (jsdo, success, request) {
// afterFill event handler statements ...
}
} ]
}
});
// JSDO access continues ...
// Login error begins ...
The fragment shows the setting of the authenticationModel property on the Session
object, pdsession, to code for the Web server HTTP Basic Authentication model for
which the Mobile Web application is configured. After logging into the Mobile Web
application with its relative URI, /SportsMobile, the code tests for the success of the
login, and for a positive test, immediately loads the JSDO catalog for the
SportsMobileSvc service.
It then instantiates a JSDO using an initialization object passed to the constructor,
which specifies the:
• Mobile resource, dsCustomer
• Setting of the initialization property, autoFill, to invoke the fill( ) method
upon instantiation
• Subscription of an in-line function to the afterFill event to check the results of
the fill( ) method
OpenEdge ® Development: Mobile Applications 105