Device Capabilities

Jetspeed capabilities provides a mechanism for mapping the client (browser) used to access the portal to media types for page rendering.

A device is associated with a list of capabilities, allowing the portal to know what kind of content the device can handle (such as Javascript, DHTML..)

The rules for mapping devices to media types and capabilities are stored in the database. The original values for these are first populated with XML data.

Your custom build should be setup with the default XML data for devices and media types. Currently there is no administrative portlets for editing device information.

A full set of capabilities, devices, media types and mime types are supplied with the XML test data.

The Jetspeed-2 capability engine maps clients to media types to mime types. Here are some more detailed definitions:

  • Clients: The application that initiates a request to the Jetspeed-2 portal engine. Jetspeed-2 uses the User-Agent to determine the client that initiates a request.
  • Media Type: The type of media requesting the content (HTML, WML, etc.). Content in Jetspeed-2 can be requested by different type of devices through different media.
  • Mime Type: The type of content being requested.
  • Supported Media Types: HTML, XHTML-BASIC, XML, WML, VXML

Define the default mime types


Define media types (used in special _control folder processing) and preferred mime type:

<MediaType name="html">
	<charcterSet value="UTF-8"/>
	<title value="HTML"/>
	<description value="Rich HTML for HTML 4.0 compliants browsers"/>

Defines supported Clients (browsers) by the portal and their device capabilities. Clients are mapped to media types via the preferred mime type

<Client name="ie5mac" evalOrder="1" preferredMimeTypeID="text/html">
	<userAgentPattern value=".*MSIE 5.*Mac.*"/>
	<version value="5.*"/>
	<model value="None"/>
	<manufacturer value="Microsoft"/>