[
https://issues.apache.org/jira/browse/SYNCOPE-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16925512#comment-16925512
]
Misagh Moayyed commented on SYNCOPE-175:
----------------------------------------
I'd suggest that we close out this one as WONT-FIX. Portlets are quite largely
deprecated and disputed as viable options in today's portals. Portals seem to
prefer web content that is not shackled by the boundaries of the JSR-186/286
specifications. The uPortal project, [https://github.com/Jasig/uPortal], while
itself does support portlets, has opted into using alternative strategies that
are more REST friendly than portlets, and I suspect others such as Liferay have
begun to take on similar approach. A full page refresh, as I think is required
by the portlet spec is generally not something a portal adopter might want to
deploy.
I admit that I have not reviewed the 3rd version of the spec quite thoroughly,
but it might be a case of too little/too late at the moment.
> End-user JSR-286 portlet
> ------------------------
>
> Key: SYNCOPE-175
> URL: https://issues.apache.org/jira/browse/SYNCOPE-175
> Project: Syncope
> Issue Type: Wish
> Reporter: Francesco Chicchiriccò
> Priority: Minor
> Fix For: 4.0.0
>
>
> Provide a portlet for end-user interface in portal environments.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
