Viewer only pages

If your JSP page contains only the viewer and nothing else, several things can be done ways to simplify the report viewing implementation.

Setting the setOwnPage property

The viewer is capable of generating complete HTML pages and can set the appropriate page properties depending on the viewing context. Setting the setOwnPage property to true provides several benefits, by allowing the viewer to completely handle the surrounding HTML content. Allowing the viewer to handle the surrounding HTML content reduces the amount of code you need to add to your JSP page and allows the viewer to automatically determine certain settings:

It allows the viewer to choose which page start and end tags to use based on what device is being used to view the page.
For example, it writes out the <html> start tag for web browsers and <wml> start tag for mobile devices.
It correctly sets the content-type and charset information for the page. This ensures that pages containing international characters is displayed correctly.

If setOwnPage is false, the surrounding HTML tags and content-type and charset directives need to be manually set.

Using the processHttpRequest method

When setOwnPage is set to true, you must use the processHttpRequest method to display the report instead of getHtmlContent. The processHttpRequest method must be used because using getHtmlContent has the same effect as setting setOwnPage to false, negating any of the benefits gained from setting setOwnPage to true.

Crystal Decisions
http://www.crystaldecisions.com/
Support services
http://support.crystaldecisions.com/