You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Patrick Cornelißen (Commented JIRA)" <ji...@apache.org> on 2012/02/12 10:40:59 UTC
[jira] [Commented] (TAP5-64) Support Java Portlet Specification V2
- JSR-286
[ https://issues.apache.org/jira/browse/TAP5-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206383#comment-13206383 ]
Patrick Cornelißen commented on TAP5-64:
----------------------------------------
Due to the raising adoption of portal servers like liferay in for example Germany, I see a definitive need for portlet support in the major frameworks. I have encountered quite a few projects that had to be ported from servlet to portlet and when the framework has no support, you have to rewrite almost the whole app. I don't think that this helps tapestry if the devs simply ignore that.
I for myself won't use tapestry for a coming project, because I know that it needs to run in a portal server later...
Just my 2c
> Support Java Portlet Specification V2 - JSR-286
> -----------------------------------------------
>
> Key: TAP5-64
> URL: https://issues.apache.org/jira/browse/TAP5-64
> Project: Tapestry 5
> Issue Type: New Feature
> Affects Versions: 5.0.15
> Reporter: Jan Vissers
> Attachments: tapestry_portlet_5.0.15.zip, tapestry_portlet_5.0.18.zip, tapestry_portlet_5.1.0.5.zip
>
>
> Specification will be finished early 2008. We need a framework that allows us to write JSR-286 portlets, would be nice if we could stick with T5 for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira