click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian A. (JIRA)" <>
Subject [jira] [Commented] (CLK-675) Portlet Support in Click
Date Sat, 02 Nov 2013 15:10:19 GMT


Adrian A. commented on CLK-675:

> The main reason for portlet support, is in my case the authentication/authorization access,
not the gui.

IMO that part can be achieved using Apache Shiro: no need for click to support portlets.

> Portlet Support in Click
> ------------------------
>                 Key: CLK-675
>                 URL:
>             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

View raw message