Optimize Performance With The Jsp Tag Library - BEA WebLogic User Manual

Part III Fundamentals of Mobile Content
"false"will discontinue syntax checking and will result in an increased performance overhead
when processing content for a full browser and is not recommended.
Exception Handling and Diagnostics
If an exception is generated while processing the JSP tags, a
javax.servlet.jsp.JSPTagException
trying to process an incorrect tag attribute. A try-catch-finally block can be added to intercept the
exception; otherwise the error will be displayed in the Application Server console.
Other information can be gathered using output from the Diagnostic Console. Diagnostic
messages are produced during the processing of the JSP tags and can be helpful for
troubleshooting. For more information on diagnostics, see the section "Work with Diagnostics."

Optimize Performance with the JSP Tag Library

As was mentioned in the previous section, many performance gains can be realized by using the
WebLogic Mobility Server JSP tag library to mobilize web content that is being requested by the
full browser device class. This section explains the ways to realize the most benefit from these
enhancements.
WebLogic Mobility Server Transformation Steps
There are several steps involved in the WebLogic Mobility Server transformation process. Some
of these steps can by bypassed to achieve optimal performance using the WebLogic Mobility
Server JSP tag library.
The typical set of steps is as follows:
•
Device recognition
•
Buffer set up
•
Content execution (either by WebLogic Mobility Server or the tag library)
•
Content check
•
Content transformation
•
Buffer flush (output)
The WebLogic Mobility Server JSP tag library is able to streamline the process of delivering
content to a full browser device by doing much of the pre-processing itself. The required mobility
tags for full browser are run and remaining tags stripped off. This allows some of the WebLogic
Mobility Server transformation processing (Step 5) to be bypassed.
There are several ways to make these optimizations:
•
Changing properties in the mis.properties file.
(<webapp dir>\WEB-INF\classes\mis.properties)
•
Setting attributes of the
•
Placing a device.xml file in
WEB-INF\classes\com\mobility\util
24 - BEA WebLogic Mobility Server User Guide
will be thrown. This might occur, for example, when
tag.
<mm:page>
he following folder to emulate a full browser device profile:
t