Fixed Issues in 2.1 ESD #3 Patch 01

The 2.1 ESD #3 Patch 01 fixes functionality in Sybase Unwired Platform 2.1 ESD #3.

The following items, identified as Known Issues in the Release Bulletin 2.1 ESD #3, are fixed in 2.1 ESD #3 Patch 01. For a complete list of fixes, see the README for Sybase Unwired Platform 2.1 ESD #3 Patch 01.

Issue Number	Description
CR 709396	For Online Data Proxy, any back-end datasource could push data to Unwired Server without authentication. Fix: For any back-end datasource to push data to Unwired Server, it must use SUP DCN user credentials for authentication. References: See SUP DCN User Role in Sybase Control Center for Sybase Unwired Platform and Mapping Roles for Domains, Packages, or Applications in Security.
CR 709392	Missing error code methods for the BlackBerry client in com.sybase.persistence.SynchronizationContext. This was a known issue for native Object API. Fix: The BlackBerry client now has the following Object API methods for getting and settings error codes and messages in com.sybase.persistence.SynchronizationContext: getErrorCode setErrorCode getErrorMessage setErrorMessage
CR 709335	For Online Data Proxy, any back-end datasource could communicate with Unwired Server without being registered in Sybase Control Center. Fix: In addition to the application endpoint, you must register any URL that is required by an application for a proxy service to enable communication with Unwired Server. References: See Proxy Properties.
CR 707616	When writing a Hybrid Web Application for iOS using the PhoneGap API navigator.camera.getPicture() and specifying FILE_URI as the destination type, you cannot display the image. The same is true for the result of any call to FileEntry.toURI(), DirectoryEntry.toURI(), or anything else that references file URIs. This was a known issue for Hybrid Web Container. Fix: The library now loads files using a file URI. This allows the workflow to access other URIs and make http requests to the native code. References: See Content Security on iOS Devices in Developer Guide: Mobile Workflow Packages.
CR 704758	Cannot delete replication devices in Sybase Control Center; license information incorrect. This was a known issue for Sybase Control Center. Fix: If the RBS application client runtime version is older than 2.1.2, delete an MBO package user to free up the license as long as the replication device has no other package users registered for other MBO packages. If the RBS application client runtime version is 2.1.2 or later, delete the application connection.