XDIME portlet design tips
This section provides design guidelines for XDIME portlets.
Splitting lengthy content into manageable parts
To accommodate the limited storage on smaller devices, you can split lengthy content into manageable parts.
Creating device-specific portlet content using Multi-Channel Server APIs
You can create device-specific content by retrieving device policy values.
Creating device-specific portlet content using conditional XDIME markup
You can create device-specific portlet content using conditional XDIME markup within your portlet JSP.
Encoding text for special XML characters
You may find it advantageous to use JSTL to encode XML characters for XDIME content
Handling cached form variables for WML devices
You can use an XDIME refresh tag to clear WML variables.
Locating assets
It is possible to reference an asset both inside and outside of the portlet's WAR file.
Accessing required Mariner Servlet objects from a portlet
There are several
Multi-Channel Server
(
MCS
) APIs that require Mariner Servlet objects. You can access the most common Mariner Servlet objects from a portlet.
Parent topic:
Developing mobile portlets