

PROVIDER REGISTRY TAG REFERENCE
===============================

Provider tag:

   Tag: <provider>
   Syntax: <provider class="java_class_name"> ... </provider>
   Example: <provider class="oracle.portal.provider.v1.http.DefaultProvider">
   
   Notes: The provider tag contains a single mandatory attribute:
     1) class:   value names the java class that implements this provider, e.g.
                 "oracle.portal.provider.v1.http.DefaultProvider".


DefaultProvider meta-data tags:
       Tags used in the body of <provider> when the class is 
       oracle.portal.provider.v1.http.DefaultProvider or a subclass.

    Tag: <session>
    Syntax: <session>true | false</session>
    Example: <session>true</session>
    Notes: The session tag defines whether this provider should create/start a
           (servlet) session in its InitSession method. This tag is optional.
           If not specified the default is true.

    Tag: <useOldStyleHeaders>
    Syntax: <useOldStyleHeaders>true | false</useOldStyleHeaders>
    Example: <useOldStyleHeaders>false</useOldStyleHeaders>

    Notes: The useOldStyleHeaders tag specifies whether or not
           PortletRendererUtil should render headers and footers for this
           provider's portlets in the style used by a 3.0.6 portal or earlier,
           rather than the style used by a post-3.0.6 portal. If your provider
           is running against a 3.0.6 portal or earlier version, it is
           recommended that you specify this tag with a value of true. This tag
           is optional. If not specified the default is false.

Portlet tags:

   Tag: <portlet>
   Syntax: <portlet class="java_class_name"> ... </portlet>
   Example: <portlet class="oracle.portal.provider.v1.http.DefaultPortlet"> 
   Notes:  The portlet tag contains a single mandatory attribute
     1) class: value names the java class that implements this portlet, e.g.
               "oracle.portal.provider.v1.http.DefaultPortlet".

MutablePortlet meta-data tags:
       Tags used in the body of <portlet> when the class implements the
       oracle.portal.provider.v1.MutablePortlet interface.

    Tag: <id>
    Syntax: <id>number</id>
    Example: <id>1</id>
    Notes: The id tag specifies this portlet's unique identifier within this provider.
           This tag is required.  It need not be sequential but must be unique within
           this provider.

    Tag: <resource>
    Syntax: <resource>class_name</resource>
    Example: <resource>oracle.portal.sample.v1.devguide.helloworld.resource.HelloWorldBundle</resource>
    Notes: The resource tag names the java ResourceBundle class for this
           portlet. Mutli-language portlets put their Portlet meta-data (title,
           name, etc) in resource bundles. This tag identifies the resource
           bundle containing these values. This tag is optional (Note: if you
           use a resource bundle for the Portlet meta-data strings you must not
           have (default) entries for these strings in the <portlet> body).

    Tag: <name>
    Syntax: <name>string</name>
    Example: <name>HelloWorld</name>
    Notes: The name tag defines the portlet's internal portal name.  The name must contain
           only alphanumeric characters without spaces. This tag is required.

    Tag: <title>
    Syntax: <title>string</title>
    Example: <title>Hello World Portlet</title>
    Notes: The title tag specifies this portlet's display name. This tag is required.

    Tag: <description>
    Syntax: <description>string</description>
    Example: <description>The Hello World Portlet outputs a salutation to the current user.</description>
    Notes: The description tag provides more detail about the portlet. The description
           is displayed to the user when she views the portlet repository (adds a portlet).
           This tag is optional but strongly recommended.

    Tag: <timeout>
    Syntax: <timeout>seconds</timeout>
    Example: <timeout>10</timeout>
    Notes: The timeout tag defines the maximum number of seconds the portal will wait for
           a response from this portlet before timing out. This tag is optional.  If not
           specified, the Portal uses the provider timeout registered by the administrator.

    Tag: <timeoutMessage>
    Syntax: <timeoutMessage>string</timeoutMessage>
    Example: <timeoutMessage>The Hello World Portlet is currently busy.  Please try again.</timeoutMessage>
    Notes: The timeoutMessage tag specifies the message the portal displays to
           the user if a response from this portlet times out. This tag is
           optional. If not specified, the Portal uses the provider
           timeoutMessage registered by the administrator.

    Tag: <showEdit>
    Syntax: <showEdit>true | false</showEdit>
    Example: <showEdit>true</showEdit>
    Notes: The showEdit tag defines if this portlet supports user customization.  This tag
           is optional.  If not specified the default is false.

    Tag: <showEditToPublic>
    Syntax: <showEditToPublic>true | false</showEditToPublic>
    Example: <showEditToPublic>true</showEditToPublic>
    Notes: The showEditToPublic tag defines whether the public user can customize this portlet.  This tag
           is optional.  If not specified the default is false.  That is the public
           user can not customize this portlet.

    Tag: <showEditDefault>
    Syntax: <showEditDefault>true | false</showEditDefault>
    Example: <showEditDefault>true</showEditDefault>
    Notes: The showEditDefault tag defines if this portlet supports default (system)
           customization.  This tag is optional.  If not specified the default is false.

    Tag: <showPreview>
    Syntax: <showPreview>true | false</showPreview>
    Example: <showPreview>true</showPreview>
    Notes: The showPreview tag defines if this portlet supports the preview mode.  This tag
           is optional.  If not specified the default is false.

    Tag: <showDetails>
    Syntax: <showDetails>true | false</showDetails>
    Example: <showDetails>true</showDetails>
    Notes: The showDetails tag defines if this portlet supports the detailed view mode.
           This tag is optional.  If not specified the default is false.

    Tag: <hasHelp>
    Syntax: <hasHelp>true | false</hasHelp>
    Example: <hasHelp>true</hasHelp>
    Notes: The hasHelp tag defines if this portlet can render a help screen.  This tag
           is optional.  If not specified the default is false.

    Tag: <hasAbout>
    Syntax: <hasAbout>true | false</hasAbout>
    Example: <hasAbout>true</hasAbout>
    Notes: The hasAbout tag defines if this portlet can render an about screen.  This tag
           is optional.  If not specified the default is false.

    Tag: <defaultLocale>
    Syntax: <defaultLocale>language.country</defaultLocale>
    Example: <defaultLocale>en.US</defaultLocale>
    Notes: The defaultLocale tag specifies the language this portlet
           renders by default.  The value is the two letter ISO language and
           country codes expressed as "language.country". This tag
           is optional.  If not specified the language and country represented
           by the the Java VMs default locale is used.

    Tag: <acceptContentType>
    Syntax: <acceptContentType>mime_type</acceptContentType>
            .....
    Example: <acceptContentType>text/html</acceptContentType>
             <acceptContentType>text/xml</acceptContentType>
    Notes: The acceptContentType tag adds to the set of mime-types this portlet
           can render. Currently unused, this will ultimately be used by the
           portal to determine if the portlet can render appropriately for the
           target user device. This tag is optional. If not specified the
           default set will include "text/html".

    Tag: <inputParameter>
    Syntax: <inputParameter class="className" >
               <name>string</name>
               <type>string | integer | number | currency | date</type>
               <description>string</description>
            </inputParameter>
            .....
    Example: <inputParameter class="oracle.portal.provider.v1.PortletParameter">
               <name>symbol</name>
               <type>string</type>
               <description>Stock symbol</description>
             </inputParameter>
    Notes: The inputParameter tag adds to the set of parameters this portlet
           recognizes. The tag contains a single required attribute, "class".
           This attribute defines the class that implements the parameter
           (should be "oracle.portal.provider.v1.PortletParameter"). This tag
           is optional. If not specified the default is there are no published
           input parameters.


Portlet Controller tags:

    Tag: <renderer>
    Syntax: <renderer class="className" >
    Example: <renderer class="oracle.portal.provider.v1.RenderManager">
               <appPath>/lottery</appPath>
               <appRoot>\jpdk\htdocs\lottery</appRoot>
               <charSet>UTF-8</charSet>
               <contentType>text/html</contentType>
               <showPage>lotto.jsp</showPage>
               <editPage>custom.jsp</editPage>
               <aboutPage>about.html</aboutPage>
               <helpPage>help.html</helpPage>
               <renderContainer>true</renderContainer>
             </renderer>
    Notes: The renderer tag defines this portlet's renderer. This tag is
           required. The tag contains a single required attribute, "class".
           This attribute defines the class that implements the renderer. Each
           renderer may define its own tags to allow further customization. See
           below for the specific tags supported by the built-in RenderManager
           class.

    Tag: <personalizationManager>
    Syntax: <personalizationManager class="className" >
    Example: <personalizationManager class="oracle.portal.provider.v1.FilePersonalizationManager">
               <dataClass>oracle.portal.provider.v1.PersonalizationObject</dataClass>
               <useHashing>true</useHashing>
             </personalizationManager>

    Notes: The personalizationManager tag defines this portlet's
           personalization manager. This tag is optional. If not specified it
           indicates this portlet doesn't support personalization. The tag
           contains a single required attribute, "class". This attribute
           defines the class that implements the personalization manager. Each
           personalization manager may define its own tags to allow further
           customization. See below for the specific tags supported by the
           built-in FilePersonalizationManager class.

    Tag: <securityManager>
    Syntax: <securityManager class="className" >
    Example: <securityManager class="myProvider.SecurityManager">
               ....
             </securityManager>
    Notes: The securityManager tag defines this portlet's security manager.
           This tag is optional. If not specified it indicates this portlet
           authorizes access to all users. The tag contains a single required
           attribute, "class". This attribute defines the class that implements
           the security manager. Each security manager may define its own tags
           to allow further customization.

RendererManager tags:
       Tags used in the body of <renderer> when the renderer is
       oracle.portal.provider.v1.RenderManager or a subclass.

    Tag: <editFormParameter>
    Syntax: <editFormParameter>string</editFormParameter>
    Example: <editFormParameter>hw_action</editFormParameter>
    Notes: Defines the name of the hidden parameter used on customize forms to
           hold the submitted 'action' (e.g. "OK" or "APPLY"). This tag is
           optional. If not specified, then the parameter name is derived from
           the portlet id.

    Tag: <renderContainer>
    Syntax: <renderContainer>true | false</renderContainer>
    Example: <renderContainer>true</renderContainer>
    Notes: Defines whether the RenderManager should automatically render the
           portlet's container (border and title) before and after
           processing/invoking the page. This tag is optional. If not specified
           the RenderManager will render the portlet's container.

    Tag: <renderCustomize>
    Syntax: <renderCustomize>true | false</renderCustomize>
    Example: <renderCustomize>false</renderCustomize>
    Notes: If renderContainer is true, defines whether the RenderManager should
           automatically render the portlet's container (border and title) in
           "Edit" and "EditDefaults" modes before and after processing/invoking
           the page. This tag is optional. If not specified the RenderManager
           will render the portlet's customize container.

    Tag: <contentType>
    Syntax: <contentType>mime_type</contentType>
    Example: <contentType>text/html</contentType>
    Notes: Defines the MIME type to be used as the default content type for
           each ManagedRenderer owned by this RenderManager. This default may
           be overridden for an individual ManagedRenderer by defining a
           content type within its 'Page' tag (see <showPage> below for an
           example). This tag is optional. If unspecified, the value
           "text/html" is assumed.

    Tag: <pageExpires>
    Syntax: <pageExpires>minutes</pageExpires>
    Example: <pageExpires>60</pageExpires>
    Notes: Defines the default expiration time (in minutes) of pages produced
           by this RenderManager's ManagedRenderers (excluding pages produced
           in "Edit" or "EditDefaults" mode). If zero, indicates that pages
           should not be cached by default. This default may be overridden for
           an individual ManagedRenderer by defining a pageExpires within its
           'Page' tag (see <showPage> below for an example). This tag is
           optional. If unspecified, a zero value is assumed.

    Tag: <appPath>
    Syntax: <appPath>virtual_path</appPath>
    Example: <appPath>/helloworld</appPath>
    Notes: The appPath specifies the default virtual path root used by this
           RenderManager's 'Page' ManagedRenderers (e.g. JspRenderer and
           FileRenderer). This default may be overridden for an individual Page
           ManagedRenderer by defining an appPathwithin its 'Page' tag (see
           <showPage> below for an example). This tag must be specified if a
           'Page' definition exists that does not define an appPath.

    Tag: <appRoot>
    Syntax: <appRoot>physical_path</appRoot>
    Example: <appRoot>\htdocs\helloworld</appRoot>
    Notes: The appRoot specifies the default physical path root used by this
           RenderManager's 'Page' ManagedRenderers. This default may be
           overridden for an individual Page ManagedRenderer by defining an
           appRoot within its 'Page' tag (see <showPage> below for an example).
           This tag must be specified if a 'Page' definition exists that does
           not define an appRoot.

    Tag: <pageParameterName>
    Syntax: <pageParameterName>string</pageParameterName>
    Example: <pageParameterName>symbol</pageParameterName>
    Notes: Defines the the default name of the request parameter that is used
           to override the name of the page used by this RenderManager's 'Page'
           ManagedRenderers. Used by portlets that render a series of screens
           to indicate to the RenderManager the request parameter that
           identifies the "next" page. This default may be overridden for an
           individual Page ManagedRenderer by defining a pageParameterName
           within its 'Page' tag (see <showPage> below for an example). This
           tag is optional.

    Tag: <charSet>
    Syntax: <charSet>iana_charset</charSet>
    Example: <charSet>UTF-8</charSet>
    Notes: Defines the default IANA character encoding to be used to decode
           pages used by this RenderManager's 'Page' ManagedRenderers. This
           default may be overridden for an individual Page ManagedRenderer by
           defining a charSet within its 'Page' tag (see <showPage> below for
           an example). This tag is optional. If unspecified, the value "UTF-8"
           is assumed.

    Tag: <showPage>
    Syntax (simple)   : <showPage>file</showPage>
    Syntax (extended) : <showPage class="managed_renderer_class">
                          <contentType>mime_type</contentType>
                          ...
                        </showPage>
    Example (simple)   : <showPage>hello.jsp</showPage>
    Example (extended) : <showPage class="oracle.portal.provider.v1.http.FileRenderer">
                           <name>hello.html</name>
                           <contentType>text/html</contentType>
                           <pageExpires>1</pageExpires>
                           <appPath>/helloworld</appPath>
                           <appRoot>\htdocs\helloworld</appRoot>
                           <pageParameterName>symbol</pageParameterName>
                           <charSet>ISO-8859-4</charSet>
                         </showPage>
                         <showPage class="oracle.portal.provider.v1.http.JspRenderer">
                           <contentType>text/vnd.oracle.mobilexml</contentType>
                           <name>mobile.jsp</name>
                         </showPage>

    Notes: Registers a ManagedRenderer that renders this portlet's "Show" mode.
           This tag (along with the other 'Page' tags) now has a 'simple' and
           'extended' form.

           In 'simple' form, the tag is assumed to describe a 'Page'
           ManagedRenderer (JspRenderer or FileRenderer) for a page whose name
           is denoted by the enclosed text, and content type is defined by the
           <contentType> tag of the parent <renderer> tag (or "text/html" if
           there is no such tag). In this case, the specific class of Page
           ManagedRenderer is decided by the page name - JspRenderer if the
           name is suffixed with ".jsp" or ".sqljsp", or FileRenderer
           otherwise. The ManagedRenderer inherits all its other properties
           from the 'defaults' set at RenderManager level.

           In extended form, the specific class of ManagedRenderer to be used
           is controlled by the mandatory "class" attribute, and the individual
           properties of that renderer are controlled by child tags specific to
           that class. All the supplied ManagedRenderers (JspRenderer,
           FileRenderer, Servlet20Renderer, JavaRenderer) support <contentType>
           and <pageExpires> child tags, which allow control over the content
           type and expiry time over the output produced by each
           ManagedRenderer. JspRenderer and FileRenderer support further
           properties which are 'defaultable' at RenderManager level (see the
           descriptions of the ManagedRenderers below).

           If multiple <showPage> tags with different <contentType> child tags
           are included, RenderManager will choose the first showPage
           definition whose content type matches the preferred content type of
           the incoming render request. This allows a RenderManager to be
           configured so that it supports 'standard' browsers (e.g. with a
           "text/html" content type) as well as mobile devices (e.g. with a
           "text/vnd.oracle.mobilexml" content type).

    Tag: <showDetailsPage>
    Syntax (simple): <showDetailsPage>file</showDetailsPage>
    Example (simple): <showDetailsPage>helloDetails.jsp</showDetailsPage>
    Notes: Registers a ManagedRenderer that renders this portlet's
           "ShowDetails" mode. This tag (along with the other 'Page' tags) now
           has a 'simple' and 'extended' form. See the <showPage> example above
           for more details. This tag is optional. If not specified for the
           preferred content type of the render request and the portlet enables
           showDetails then the <showPage> renderer is used.

    Tag: <previewPage>
    Syntax (simple): <previewPage>file</previewPage>
    Example (simple): <previewPage>helloPreview.jsp</previewPage>
    Notes: Registers a ManagedRenderer that renders this portlet's "Preview"
           mode. This tag (along with the other 'Page' tags) now has a 'simple'
           and 'extended' form. See the <showPage> example above for more
           details. This tag is only required if the portlet enables/supports
           preview.

    Tag: <editPage>
    Syntax (simple): <editPage>file</editPage>
    Example (simple): <editPage>custom.jsp</editPage>
    Notes: Registers a ManagedRenderer that renders this portlet's "Edit" mode.
           This tag (along with the other 'Page' tags) now has a 'simple' and
           'extended' form. See the <showPage> example above for more details.
           This tag is optional. If not specified for the preferred content
           type of the render request and the portlet enables user
           customization then the <editDefaultsPage> must be specified for that
           content type as it becomes the default.

    Tag: <editDefaultsPage>
    Syntax (simple): <editDefaultsPage>file</editDefaultsPage>
    Example (simple): <editDefaultsPage>custom.jsp</editDefaultsPage>
    Notes: Registers a ManagedRenderer that renders this portlet's
           "EditDefaults" mode. This tag (along with the other 'Page' tags) now
           has a 'simple' and 'extended' form. See the <showPage> example above
           for more details. This tag is optional. If not specified for the
           preferred content type of the render request and the portlet enables
           user customization then the <editPage> must be specified for that
           content type as it becomes the default.

    Tag: <aboutPage>
    Syntax (simple): <aboutPage>file</aboutPage>
    Example (simple): <aboutPage>about.html</aboutPage>
    Notes: Registers a ManagedRenderer that renders this portlet's "About"
           mode. This tag (along with the other 'Page' tags) now has a 'simple'
           and 'extended' form. See the <showPage> example above for more
           details. This tag is only required if the portlet enables/supports
           displaying an about screen.

    Tag: <helpPage>
    Syntax (simple): <helpPage>file</helpPage>
    Example (simple): <helpPage>help.html</helpPage>
    Notes: Registers a ManagedRenderer that renders this portlet's "Help" mode.
           This tag (along with the other 'Page' tags) now has a 'simple' and
           'extended' form. See the <showPage> example above for more details.
           This tag is only required if the portlet enables/supports displaying
           help.

    Tag: <linkPage>
    Syntax (extended) : <linkPage class="managed_renderer_class">
                          <contentType>mime_type</contentType>
                          ...
                        </linkPage>
    Example (extended) : <linkPage class="oracle.portal.provider.v1.http.JspRenderer">
                           <contentType>text/vnd.oracle.mobilexml</contentType>
                           <name>link.jsp</name>
                         </linkPage>
    Notes: Registers a ManagedRenderer that renders this portlet's "Link" mode.
           This tag (along with the other 'Page' tags) now has a 'simple' and
           'extended' form. See the <showPage> example above for more details.
           This mode is generally only used by mobile devices to display a link
           to the Show mode page. Hence the tag should generally be used with
           the "text/vnd.oracle.mobilexml" content type.

    Tag: <defaultPage>
    Syntax (simple): <defaultPage>file</defaultPage>
    Example (simple): <defaultPage>help.html</defaultPage>
    Notes: Registers a ManagedRenderer that renders this portlet's 'default'
           page. This page is used when no ManagedRenderer has been specified
           for the specific mode of the render request. This tag (along with
           the other 'Page' tags) now has a 'simple' and 'extended' form. See
           the <showPage> example above for more details.

FilePersonalizationManager tags:
       Tags used in the body of <personalizationManager> when the class is 
       oracle.portal.provider.v1.FilePersonalizationManager.

    Tag: <dataClass>
    Syntax: <dataClass>class_name</dataClass>
    Example: <dataClass>oracle.portal.provider.v1.PersonalizationObject</dataClass>
    Notes: Class name for this portlet's customization data object.  This tag is required.

    Tag: <rootDirectory>
    Syntax: <rootDirectory>physical_path</rootDirectory>
    Example: <rootDirectory>D:\customization_data</rootDirectory>
    Notes: The rootDirectory tag sets the path to the filesystem directory
           under which personalization data will be stored for the portlet
           owning this personalization manager. This tag is optional. If not
           specified, the provider's application root directory, specified via
           the "provider_root" initArg, will be used.

    Tag: <useHashing>
    Syntax: <useHashing>true | false</useHashing>
    Example: <useHashing>true</useHashing>
    Notes: The useHashing tag specifies whether the 'path hashing' feature
           should be used when determining the filesystem path in which to
           store a customization data file for a particular portlet instance.
           If the value is false, then all customization data files for a
           portlet instance will be stored in a single directory corresponding
           to that portlet instance. If the value is true, then an extra level
           of directories below the portlet instance directory, with names
           derived by a hash function of the customization data file name, will
           be used in order to limit the number of customization data files
           stored in a single directory. This tag is optional. If not specified
           the default is false.

Tags common to all ManagedRenderers:
       These tags are common to all ManagedRenderers (JspRenderer, FileRenderer,
       Servlet20Renderer and JavaRenderer).

    Tag: <contentType>
    Syntax: <contentType>mime_type</contentType>
    Example: <contentType>text/html</contentType>
    Notes: See tag reference for RenderManager. Any value set here will
           override that set at RenderManager level

    Tag: <pageExpires>
    Syntax: <pageExpires>minutes</pageExpires>
    Example: <pageExpires>60</pageExpires>
    Notes: See tag reference for RenderManager. Any value set here will
           override that set at RenderManager level

JspRenderer, FileRenderer common tags:
       Tags used when the "managed_renderer_class" is 
       oracle.portal.provider.v1.http.JspRenderer or
       oracle.portal.provider.v1.http.FileRenderer.

    Tag: <appPath>
    Syntax: <appPath>virtual_path</appPath>
    Example: <appPath>/helloworld</appPath>
    Notes: See tag reference for RenderManager. Any value set here will
           override that set at RenderManager level

    Tag: <appRoot>
    Syntax: <appRoot>physical_path</appRoot>
    Example: <appRoot>\htdocs\helloworld</appRoot>
    Notes: See tag reference for RenderManager. Any value set here will
           override that set at RenderManager level

    Tag: <charSet>
    Syntax: <charSet>iana_charset</charSet>
    Example: <charSet>UTF-8</charSet>
    Notes: See tag reference for RenderManager. Any value set here will
           override that set at RenderManager level

    Tag: <pageParameterName>
    Syntax: <pageParameterName>string</pageParameterName>
    Example: <pageParameterName>symbol</pageParameterName>
    Notes: See tag reference for RenderManager. Any value set here will
           override that set at RenderManager level

    Tag: <name>
    Syntax: <name>appRoot_relative_file_name</name>
    Example: <name>lotto.jsp</name>
    Notes: Defines the <appRoot> relative name of the file used to render the
           contents of this page.

JspRenderer, Servlet20Renderer common tags:
       Tags used when the "managed_renderer_class" is 
       oracle.portal.provider.v1.http.JspRenderer or
       oracle.portal.provider.v1.http.Servlet20Renderer.

    Tag: <parameter>
    Syntax: <parameter class="parameter_class">
              ...
            </parameter>
    Example: <parameter class="oracle.portal.utils.v1.NameValuePair">
               <name>id</name>
               <value>147</value>
             </parameter>
    Notes: The class which will be instantiated to wrap up this <parameter> is
           defined in the required "class" attribute. These parameters will
           then be available from the HttServletRequest object given to the JSP
           or servlet used to render this page. To implement this functionality,
           use the NameValuePair class supplied with the JPDK (see below).

Servlet20Renderer specific tags:
       Tags used when the "managed_renderer_class" is 
       oracle.portal.provider.v1.http.Servlet20Renderer 

    Tag: <servletClass>
    Syntax: <servletClass>my.servlet.class</servletClass>
    Example: <servletClass>oracle.portal.sample.v1.devguide.helloservletworld.ShowServlet</servletClass>
    Notes: Defines the fully-qualified name of the servlet class used
           to render the contents of this page.

JavaRenderer specific tags:
       Tags used when the "managed_renderer_class" is 
       oracle.portal.provider.v1.http.JavaRenderer

    Tag: <className>
    Syntax: <className>my.class.name</className>
    Example: <className>oracle.portal.sample.portlet.samplerenderer.SampleRenderer</className>
    Notes: Defines the fully-qualified class name which will be instantiated
           to render the contents for this page.

    Tag: <renderMethod>
    Syntax: <renderMethod>myMethodName</renderMethod>
    Example: <renderMethod>render</renderMethod>
    Notes: Defines the method name which will be called on an instance of
           <className> to render the contents for this page. There must be
           a method on <className> corresponding to this name which takes
           a PortletRenderRequest as its single parameter.

NameValuePair tags:
       Tags used when the "parameter_class" is oracle.portal.utils.v1.NameValuePair

    Tag: <name>
    Syntax: <name>parameter_name</name>
    Example: <name>id</name>
    Notes: Defines the name of this parameter.

    Tag: <value>
    Syntax: <value>parameter_value</value>
    Example: <value>147</value>
    Notes: Defines the value of this parameter.

