Pluto
  1. Pluto
  2. PLUTO-418

Add support for container-runtime-options

    Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.1-286-COMPATIBILITY, 2.0.0
    • Fix Version/s: 1.1-286-COMPATIBILITY, 2.0.0
    • Component/s: None
    • Labels:
      None

      Description

      PLT.10.4.:
      The portlet can define additional runtime behavior in the portlet.xml on either the
      portlet application level or the portlet level with the container-runtime-option element.
      Runtime options that are defined on the application level should be applied to all portlets
      in the portlet application. Runtime options that are defined on the portlet level should be
      applied for this portlet only and override any runtime options defined on the application
      level with the same name.
      Container runtime options are optional to support by the portlet container and the portlet
      can find out which container runtime options are supported by the portlet container
      running the portlet via the method getContainerRuntimeOptions on the
      PortletContext.

        Activity

        Hide
        Craig Doremus added a comment -

        Patch was applied to both '286' branches.

        Show
        Craig Doremus added a comment - Patch was applied to both '286' branches.
        Hide
        Craig Doremus added a comment -

        Applied container_runtime_options.plus_properties.200707.patch to 1.1-286-trunk-merge branch in SVN revs 568066 and 568069.

        Show
        Craig Doremus added a comment - Applied container_runtime_options.plus_properties.200707.patch to 1.1-286-trunk-merge branch in SVN revs 568066 and 568069.
        Hide
        Torsten Dettborn added a comment -

        Committed patch container_runtime_options.plus_properties.200707.patch, sorry eclipse hase committed project based, so the new rev numbers are 567970,567971 and 567972.

        Show
        Torsten Dettborn added a comment - Committed patch container_runtime_options.plus_properties.200707.patch, sorry eclipse hase committed project based, so the new rev numbers are 567970,567971 and 567972.
        Hide
        Christian Raschka added a comment -

        Yes. The properties are fully qualified (see PLT.10.4.) and the possible values are:

        javax.portlet.escapeXml, javax.portlet.renderHeaders, javax.portlet.includedPortletSessionScope and javax.portlet.actionScopedRequestAttributes

        I will add a comment regarding this.

        I don't know exactly how to implement the runtime option support yet. Any comments are appreciated.

        Show
        Christian Raschka added a comment - Yes. The properties are fully qualified (see PLT.10.4.) and the possible values are: javax.portlet.escapeXml, javax.portlet.renderHeaders, javax.portlet.includedPortletSessionScope and javax.portlet.actionScopedRequestAttributes I will add a comment regarding this. I don't know exactly how to implement the runtime option support yet. Any comments are appreciated.
        Hide
        Craig Doremus added a comment -

        Christian. should the value of org.apache.pluto.container.supportedContainerRuntimeOptions in pluto-configuration.properties be a fully qualified runtime option name (e.g. javax.portlet.escapeXml)? If so, can you add a comment to that effect in the properties file above this record? (I assume you use escapeXml for test purposes only).

        Also, it seems that a container is going to have to add a class to implement 'runtime option support' behavior. How is this going to be done and discovered by the container?

        Show
        Craig Doremus added a comment - Christian. should the value of org.apache.pluto.container.supportedContainerRuntimeOptions in pluto-configuration.properties be a fully qualified runtime option name (e.g. javax.portlet.escapeXml)? If so, can you add a comment to that effect in the properties file above this record? (I assume you use escapeXml for test purposes only). Also, it seems that a container is going to have to add a class to implement 'runtime option support' behavior. How is this going to be done and discovered by the container?
        Hide
        Christian Raschka added a comment -

        This patch includes the first one, plus getting the supported container runtime options out of the property file (pluto-configuration.properties)

        Show
        Christian Raschka added a comment - This patch includes the first one, plus getting the supported container runtime options out of the property file (pluto-configuration.properties)
        Hide
        Christian Raschka added a comment -

        This patch implements this feature. For now (testing) the container supported runtime options are hard coded in PortletContextImpl.java and have to be somewhere else (pluto-configuration.xml?) in the future.

        Show
        Christian Raschka added a comment - This patch implements this feature. For now (testing) the container supported runtime options are hard coded in PortletContextImpl.java and have to be somewhere else (pluto-configuration.xml?) in the future.

          People

          • Assignee:
            Unassigned
            Reporter:
            Christian Raschka
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development