OData SDK API Changes in Version 2.2

The HTTP REST client libraries are available for OData applications in 2.2 SP03. Previous changes in 2.2 SP02 included Afaria, DataVault, refactored ODP class names, and introduction of ODPException.

HTTP REST Client Libraries in 2.2 SP03

The HTTP REST client libraries are available with 2.2 SP03, which enable you to implement REST services in OData applications (Android and iOS). The REST SDK libraries enable consumption of Sybase Unwired Platform REST services with pure HTTP (by default in on-premise) connectivity. The REST SDK provides simplified APIs for registration, exchange settings between client and server, and end-to-end tracing. The SDK also supports native push notifications.

New HTTP REST Classes for OData
Classes Platform
  • ClientConnection
  • UserManager
  • AppSettings
 Android
  • SMPClientConnection
  • SMPUserManager
  • SMPAppSettings
 iOS

Documented in: Developer Guide: OData SDK, see REST SDK API Reference (Android and iOS)

Afaria APIs

Afaria APIs are no longer packaged with the OData SDK API, but are now available directly from the standalone Afaria library: http://frontline.sybase.com/support/downloads.aspx (registration required).

Afaria Methods Removed from OData SDK
Methods Platform
  • setConnectionProfileFromAfaria()
  • getSettingsFromAfaria()
  • getSignedCertificateFromAfaria()
 Android
  • setConnectionProfileFromAfaria()
  • getSettingsFromAfaria()
  • getSignedCertificateFromAfaria()
 BlackBerry
  • setConnectionProfileFromAfariaForUrl
  • getSettingsFromAfariaForUrl
  • getSignedCertificateFromAfaria
 iOS

Related topics or references have been removed from Developer Guide: OData SDK.

DataVault API

DataVault APIs are no longer packaged with the OData SDK API, but are now available from the standalone DataVault library that is packaged with the Sybase Mobile SDK.

Deleted DataVault Methods
Methods Platform
LiteDataVault Android
SUPDataVault BlackBerry
LiteSUPDataVault iOS

Related topics or references have been removed from Developer Guide: OData SDK.

ODP Class Name Changes

Some API class names have been refactored to keep naming conventions consistent across all platforms. APIs are logically grouped in the corresponding refactored classes. Also for consistency, some new classes have been added.

Changed (Refactored) Class Names
Methods Platform
  • ODPAppSettings – refactored from LiteAppSettings.
  • ODPCertificateManager – refactored from LiteCertificateStore.
  • ODPUserManager – refactored from LiteUserManager.
  • ODPException – new class.
  • ODPClientConnection – refactored from LiteMessagingClient.
 Android
  • ODPAppSettings – refactored from AppSettings.
  • ODPCertificateManager – refactored from CertificateStore
  • ODPUserManager – refactored from UserManager.
  • ODPException – new class.
  • ODPClientConnection – APIs moved into this class for logical grouping.
 BlackBerry
  • ODPAppSettings – refactored from AppSettings.
  • ODPCertificateManager – refactored from CertificateStore.
  • ODPUserManager – refactored from UserManager.
 iOS

See Developer Guide: OData SDK, the ODP SDK API Usage topic (iOS, Android, and BlackBerry sections).

ODPException API

Error codes thrown by ODP APIs are defined in the ODPException class.

See ODPException class (Android and BlackBerry) documentation in Javadoc.

Parent topic: Migrate OData Applications Using Refactored Libraries