click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CLK-675) Portlet Support in Click
Date Mon, 14 Jun 2010 11:25:14 GMT

    [ https://issues.apache.org/jira/browse/CLK-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878536#action_12878536
] 

Matthias commented on CLK-675:
------------------------------

I know, that is not a simple Task and the reason for this feature request is not the gui in
my case.
You are right that the performance in Portletserves are always poor but in our company we
must  support a Portletserver.
The main reason for portlet support, is in my case the authentication/authorization access,
not the gui.

It would be a big feature, if click supports a alternate super class page like PortletPage.















> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message