Categories: Technical Solution | Java ME | File Connection and PIM API (JSR-75) | MMAPI (JSR-135) | S60 2nd Edition | S60 3rd Edition
This page was last modified 23:36, 19 May 2008.
TSJ000424 - Saving and reading DRM-protected files using FileConnection API and Mobile Media API
From Forum Nokia Wiki
Subject: | Saving and reading DRM-protected files using FileConnection API and Mobile Media API | TSJ000424 | |
|
| Platform(s): | Device(s), SW version(s): | |
| S60 2nd Edition S60 3rd Edition | |||
Category: | Java | ||
Subcategory: | - | ||
Description: | Saving a DRM-protected file using the FileConnection API is not possible in any of the current implementations. You can download and save a .dm or .dcf file to the device’s file system, but the file won’t be DRM-protected because the only delivery methods supported normally are HTTP (via browser) and MMS. Some newer devices may support Bluetooth or e-mail, but HTTP and MMS delivery methods are the rule. Therefore, saving a .dm or .dcf file to the file system will be successful from the FC API’s standpoint, but it will be impossible to play it back from either the MMAPI or native application, because it will appear as corrupted, not being registered in the device’s DRM content database. On S60 3rd Edition devices there is some DRM support described as follows: - It is possible to open a file protected by DRM, using the following syntax: FileConnection fc = (FileConnection)Connector.open("file:///E:/Sounds/Digital/jack_aac_aac.dcf?drm=enc",Connector.READ); Note that it is only possible to open the file in read-only mode, so the Connector.READ parameter is mandatory. - It is possible to play a DRM-protected file using the Mobile Media API with the following syntax: Player p = Manager.createPlayer("file:///E:/Sounds/Digital/jack_aac_aac.dcf"); //without the drm=enc parameter p.start(); - It is still not possible to save a file with DRM protection using Java. - The example MIDlet Drmtest 3rd.zip with sample code shows how to access and play DRM-protected files on S60 3rd Edition devices. For all other devices, the behavior is as follows: - Downloading a wallpaper (.jpg) file, protected with DRM Forward Lock, and saving it via Java ME does not protect the file locally, neither makes it able to be played with the MMAPI or native applications. - Downloading a file via the browser, thus enforcing the DRM protection, and trying to access it via the Java ME FileConnection API shows that the file becomes invisible to the FileConnection.list(); methods, so the file isn’t even visible to Java, let alone playable by the MMAPI. - Forcing the absolute path of the file, as in Connector.open("file:///C:/Nokia/Images/file_protected_drm.jpg"); throws a java.lang.SecurityException: Access Denied. in both Series 40 and S60 devices. The example MIDlet Drmtest.zip with sample code shows how the attempt to access and play DRM-protected files on devices other than S60 3rd Edition causes run-time exceptions. | ||
Creation date: | October 5, 2006 | ||
Last modified: | - | ||
| Related Discussions | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| MIDP 2.0 | slashtien | Mobile Java General | 2 | 2003-07-10 07:59 |
| Missing CSendAppUi in 3rd Ed. | dathom | General Symbian C++ | 1 | 2007-07-13 05:01 |
| OMA DRM 2.0 | Haritha | Mobile Java Tools & SDKs | 1 | 2008-03-26 23:11 |
| 新新手的问题 | jeklee | Other Programming Discussion 关于其他编程技术的讨论 | 5 | 2003-12-12 05:45 |
| DRM content binding problem | Ajit | Digital Rights Management & Content Downloading | 0 | 2007-05-02 13:28 |
