You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Christian Raschka (JIRA)" <ji...@apache.org> on 2007/08/20 12:05:30 UTC
[jira] Created: (PLUTO-418) Add support for
container-runtime-options
Add support for container-runtime-options
-----------------------------------------
Key: PLUTO-418
URL: https://issues.apache.org/jira/browse/PLUTO-418
Project: Pluto
Issue Type: New Feature
Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
Reporter: Christian Raschka
Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-418) Add support for
container-runtime-options
Posted by "Christian Raschka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Raschka updated PLUTO-418:
------------------------------------
Attachment: container_runtime_options.200707.patch
> Add support for container-runtime-options
> -----------------------------------------
>
> Key: PLUTO-418
> URL: https://issues.apache.org/jira/browse/PLUTO-418
> Project: Pluto
> Issue Type: New Feature
> Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Reporter: Christian Raschka
> Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
> Attachments: container_runtime_options.200707.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (PLUTO-418) Add support for
container-runtime-options
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Doremus resolved PLUTO-418.
---------------------------------
Resolution: Fixed
Patch was applied to both '286' branches.
> Add support for container-runtime-options
> -----------------------------------------
>
> Key: PLUTO-418
> URL: https://issues.apache.org/jira/browse/PLUTO-418
> Project: Pluto
> Issue Type: New Feature
> Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Reporter: Christian Raschka
> Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
> Attachments: container_runtime_options.200707.patch, container_runtime_options.plus_properties.200707.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-418) Add support for
container-runtime-options
Posted by "Christian Raschka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Raschka updated PLUTO-418:
------------------------------------
Attachment: container_runtime_options.plus_properties.200707.patch
This patch includes the first one, plus getting the supported container runtime options out of the property file (pluto-configuration.properties)
> Add support for container-runtime-options
> -----------------------------------------
>
> Key: PLUTO-418
> URL: https://issues.apache.org/jira/browse/PLUTO-418
> Project: Pluto
> Issue Type: New Feature
> Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Reporter: Christian Raschka
> Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
> Attachments: container_runtime_options.200707.patch, container_runtime_options.plus_properties.200707.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PLUTO-418) Add support for
container-runtime-options
Posted by "Christian Raschka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521124 ]
Christian Raschka commented on PLUTO-418:
-----------------------------------------
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.
> Add support for container-runtime-options
> -----------------------------------------
>
> Key: PLUTO-418
> URL: https://issues.apache.org/jira/browse/PLUTO-418
> Project: Pluto
> Issue Type: New Feature
> Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Reporter: Christian Raschka
> Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
> Attachments: container_runtime_options.200707.patch, container_runtime_options.plus_properties.200707.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PLUTO-418) Add support for
container-runtime-options
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521396 ]
Craig Doremus commented on PLUTO-418:
-------------------------------------
Applied container_runtime_options.plus_properties.200707.patch to 1.1-286-trunk-merge branch in SVN revs 568066 and 568069.
> Add support for container-runtime-options
> -----------------------------------------
>
> Key: PLUTO-418
> URL: https://issues.apache.org/jira/browse/PLUTO-418
> Project: Pluto
> Issue Type: New Feature
> Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Reporter: Christian Raschka
> Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
> Attachments: container_runtime_options.200707.patch, container_runtime_options.plus_properties.200707.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PLUTO-418) Add support for
container-runtime-options
Posted by "Torsten Dettborn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521329 ]
Torsten Dettborn commented on PLUTO-418:
----------------------------------------
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.
> Add support for container-runtime-options
> -----------------------------------------
>
> Key: PLUTO-418
> URL: https://issues.apache.org/jira/browse/PLUTO-418
> Project: Pluto
> Issue Type: New Feature
> Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Reporter: Christian Raschka
> Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
> Attachments: container_runtime_options.200707.patch, container_runtime_options.plus_properties.200707.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-418) Add support for
container-runtime-options
Posted by "Christian Raschka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Raschka updated PLUTO-418:
------------------------------------
Attachment: container_runtime_options.200707.patch
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.
> Add support for container-runtime-options
> -----------------------------------------
>
> Key: PLUTO-418
> URL: https://issues.apache.org/jira/browse/PLUTO-418
> Project: Pluto
> Issue Type: New Feature
> Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Reporter: Christian Raschka
> Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
> Attachments: container_runtime_options.200707.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (PLUTO-418) Add support for
container-runtime-options
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521118 ]
Craig Doremus commented on PLUTO-418:
-------------------------------------
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?
> Add support for container-runtime-options
> -----------------------------------------
>
> Key: PLUTO-418
> URL: https://issues.apache.org/jira/browse/PLUTO-418
> Project: Pluto
> Issue Type: New Feature
> Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Reporter: Christian Raschka
> Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
> Attachments: container_runtime_options.200707.patch, container_runtime_options.plus_properties.200707.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (PLUTO-418) Add support for
container-runtime-options
Posted by "Christian Raschka (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Raschka updated PLUTO-418:
------------------------------------
Attachment: (was: container_runtime_options.200707.patch)
> Add support for container-runtime-options
> -----------------------------------------
>
> Key: PLUTO-418
> URL: https://issues.apache.org/jira/browse/PLUTO-418
> Project: Pluto
> Issue Type: New Feature
> Affects Versions: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
> Reporter: Christian Raschka
> Fix For: 1.1-286-COMPATIBILITY, 1.1-286-trunk-merge
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.