This guide describes how to use JMFRegistry. JMFRegistry is a stand alone Java application that you can use to register new DataSources, MediaHandlers, PlugIns, and capture devices with JMF so that they can be used with your JMF 2.0 installation. JMFRegistry also enables you to rearrange the search orders and remove registered extensions.
To use a custom DataSource or MediaHandler with JMF, you must register the package prefix that identifies where the new class is located. (For example, COM.yourbiz.) You can do this with JMFRegistry through the PackageManager tab. Package prefixes for new protocols and MediaHandlers are set separately in the protocol package-prefix list and the content package-prefix list. You can also rearrange the order in which JMF searches installed protocol and media handlers, and remove registered package prefixes from the PackageManager tab.
For more information about how package prefixes are used to locate JMF extensions, see the "Extending JMF" chapter in the JMF API Guide.
To add a package prefix to either the ProtocolPrefix List or ContentPrefix List:
To remove a package prefix from either the ProtocolPrefix List or ContentPrefix List:
To use a custom PlugIn with JMF, you must register it with the PlugInManager. You can do this with JMFRegistry through the PlugInManager tab. You can also view the input and/or output formats of a registered plug-in, rearrange the order in which JMF queries plug-ins, and remove registered plug-ins from the PlugInManager tab.
To register a new plug-in:
To remove a plug-in:
To use a particular capture device with JMF, you must register it with the CaptureDeviceManager. You can do this with JMFRegistry through the CaptureDeviceManager tab. You can also rearrange the order in which JMF queries capture devices, and remove registered devices from the CaptureDeviceManager tab.
To register a new capture device:
You can register file extension/MIME-type mappings with JMFRegistry through the MIME Types tab. A file extension can map to only one MIME type, but a MIME type can have several different file extensions mapped to it.
To add a mapping between a MIME type and a file extension:
To remove a file extension mapping for a MIME type:
To remove all of the mappings for a MIME type:
Note: You can only remove MIME types and file extensions that you have added. You cannot change or remove the default mappings. For example, you cannot remove the extension
mov or remap it to the MIME type
From the User Settings tab, you can specify file extensions that applets can read in addition to the registered mime types, control JMF Applet permissions, and control the location and size of the cache used when reading media from the network.
The Allow File Writing for Applets and Allow Capture for Applets check boxes let you control whether or not applets have permission to perform these operations.
The Allow Caching check box lets you control whether or not media content read from the network is cached to disk. If you enable media caching, you can also specify the directory where the media will be cached and how much disk space can be used for the cache.
|Registering Package Prefixes for New Protocols and Media Handlers|
|Registering New Plug-Ins|
|Registering New Capture Devices with JMF|
|Registering File Extension Mappings for MIME Types|
|Changing User Settings|
Oracle is reviewing the Sun product roadmap and will provide guidance to customers in accordance with Oracle's standard product communication policies. Any resulting features and timing of release of such features as determined by Oracle's review of roadmaps, are at the sole discretion of Oracle. All product roadmap information, whether communicated by Sun Microsystems or by Oracle, does not represent a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. It is intended for information purposes only, and may not be incorporated into any contract.