[
https://issues.apache.org/jira/browse/CLK-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrian A. resolved CLK-675.
---------------------------
Resolution: Won't Fix
SSO and Authorization integration can be achieved by using Apache Shiro or
ACEGI. A complete portlet implementation in Click would be quite heavy so I'm
closing this issue.
> Portlet Support in Click
> ------------------------
>
> Key: CLK-675
> URL: https://issues.apache.org/jira/browse/CLK-675
> Project: Click
> Issue Type: New Feature
> Components: extras
> Reporter: George Stan
> Labels: portlet
>
> Please support Portlets in Click.
> Tapestry has it, Wicket has it, and even if this is not a too good argument
> for it, I believe click should have
> some sort of Portlet support too (even if it's not in the core, but a third
> party solution).
> Many companies adopted a portal solution, so for them it's not an option
> *not* to use portlets. They use JSF,
> and Tapestry despite the fact of not being very easy to learn.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
