[
https://issues.apache.org/jira/browse/APA-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792048#action_12792048
]
Woonsan Ko commented on APA-26:
-------------------------------
By the way, I believe that this addition of custom portlet modes would not make
any harm during deployment.
According to the portlet spec (PLT.8.6), it says,
" The portlet container must ignore all references to custom portlet modes
that are not
supported by the portal implementation, or that have no mapping to portlet
modes
supported by the portal."
I think this implies the portlet container must not make failures because of
non-supportable custom modes. If the portlet container does not support some
custom modes, then it can just ignore those without affecting other behaviors
of the portlet applications.
> Add custom portlet modes in portlet application descriptors for possible
> support by the container
> -------------------------------------------------------------------------------------------------
>
> Key: APA-26
> URL: https://issues.apache.org/jira/browse/APA-26
> Project: Portals Apps
> Issue Type: Improvement
> Components: apa-dbbrowser, apa-demo, apa-rss, apa-webcontent
> Affects Versions: apa-dbbrowser-1.0 , apa-rss-1.0, apa-demo-1.0,
> apa-webcontent-1.0
> Reporter: Woonsan Ko
> Assignee: Woonsan Ko
> Priority: Minor
> Fix For: apa-dbbrowser-1.1, apa-rss-1.1, apa-demo-1.1,
> apa-webcontent-1.1
>
>
> Some portals support custom portlet modes such as 'about', 'config',
> 'edit_defaults' or "preview' which are introduced by the portlet
> specification.
> So, it would be better to include those portlet modes in the portlet
> application descriptors for possible support by the containers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
