In the article How to Build a URL-Based Portlet, you learnt how to create a portlet that displayed the content of a URL-based application. The example used in that article was Google.com. Since many URL-based applications (including Google.com) display links inside their HTML, you may find it desirable to have these links render inside the portlet container. For example, when you click on a link, you may want to see the portlet render again displaying the destination page as its content (as opposed to seeing the whole browser window display the destination page). PDK-URL Services enables you to select inline rendering as a feature for your URL-based portlets.
This article describes how to build a URL-based portlet that renders its portlet links inside the portlet container. It extends the Google.com sample found in the article, How to Build a URL-Based Portlet.
You have successfully installed the PDK-Java runtime and samples by following the article Installing the PDK-Java Framework and Samples.
You have successfully installed the PDK-URL Services runtime and samples by following the article Installing the PDK-URL Services Samples
You have successfully installed the Google.com URL-based portlet by following the article How to Build a URL-Based Portlet.
This section explains how to create an XML provider definition for your URL-based portlet provider.
The following sample is the same as that found in the article How to Build a URL-Based Portlet. It displays Google.com within the portlet. However, this time it uses the inlineRendering tag to specify that portlet links are to be rendered within the portlet container. Please refer to the article Understanding provider.xml for PDK-URL Services for an explanation of the required XML tags and their functions.
<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
<?providerDefinition version="2.0"?>
<provider class="oracle.portal.provider.v1.http.URLProvider">
<session>true</session>
<proxyInfo class="oracle.portal.provider.v1.http.ProxyInformation">
<httpProxyHost>www-proxy.us.oracle.com</httpProxyHost>
<httpProxyPort>80</httpProxyPort>
</proxyInfo>
<portlet class="oracle.portal.provider.v1.http.URLPortlet">
<id>1</id>
<name>Google.com Portlet</name>
<title>Google.com Portlet</title>
<description>Display Google.com as a portlet.</description>
<timeout>100</timeout>
<timeoutMessage>Timed out waiting for Google.com Portlet.</timeoutMessage>
<acceptContentType>text/html</acceptContentType>
<showEdit>false</showEdit>
<showEditToPublic>false</showEditToPublic>
<showEditDefault>false</showEditDefault>
<showPreview>false</showPreview>
<showDetails>false</showDetails>
<hasHelp>false</hasHelp>
<hasAbout>false</hasAbout>
<renderer class="oracle.portal.provider.v1.RenderManager">
<contentType>text/html</contentType>
<showPage class="oracle.portal.provider.v1.http.URLRenderer">
<contentType>text/html</contentType>
<charSet>ISO-8859-1</charSet>
<pageUrl>http://www.google.com</pageUrl>
<filter class="oracle.portal.provider.v1.http.HtmlFilter">
<headerTrimTag><body</headerTrimTag>
<footerTrimTag>/body></footerTrimTag>
<inlineRendering>true</inlineRendering>
</filter>
</showPage>
</renderer>
</portlet>
</provider>
|
Save the file as "provider.xml", making sure it overwrites the provider.xml file you created from the article How to Build a URL-Based Portlet (you may wish to make a backup copy of the older provider.xml file).
Since you configured and registered the Google.com portlet provider when following the article How to Build a URL-Based Portlet, you simply need to stop and restart the Oracle HTTP Server and refresh the portlet provider through the Edit Provider screen. Now you are ready to add the inline rendering-enabled Google.com portlet to a page.
Now that you have successfully added inline rendering to your URL-based portlet, please look for other portlet development articles that describe how to add extra features to your portlet, including single sign-on to external URL-based applications, HTML and XML filtering, parameter passing, and more.
Here are some reference articles to help you better understand the architecture and technical details of PDK-URL Services:
Revision History:
November 2001