[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-tabpanelfocusedCommentId=13789143#comment-13789143 ] Thiago H. de Paula Figueiredo commented on TAP5-64: --- Hi, guys! Shouldn't this issue be closed due to the tapestry5-portlet linked above? I haven't used portlets myself, so I'm not the best one to check it. If nobody says no in a couple weeks, I'll close this issue. 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 Assignee: François Facon 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 was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13789270#comment-13789270 ] Pieter Schoenmakers commented on TAP5-64: - I'd expect this issue to be closed once tap5 has out-of-the-box portlet support. (PS: I didn't check out the fine work on code or github.) 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 Assignee: François Facon 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 was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13789367#comment-13789367 ] Thiago H. de Paula Figueiredo commented on TAP5-64: --- Hello, Pieter! What do you mean by out-of-the-box portlet support? As in tapestry-core itself? I'm sorry, that's not going to happen. Not everybody which uses Tapestry uses portlets, so it doesn't make much sense to put support for it in core. The Tapestry philosophy is to have the basic functionality in tapestry-core and more specific stuff in other JARs, such as tapestry-upload and tapestry-hibernate. If it's about a separate JAR under the Apache Tapestry project, tapestry5-portlet is mostly written by Tapestry committers themselves. In addition, we avoid having too much stuff under the Tapestry project itself because we're all volutaries and we'd need to support that code. I agree with you that tapestry5-porlet should have its JAR in Maven Central Repository. Cheers! 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 Assignee: François Facon 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 was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13789426#comment-13789426 ] Pieter Schoenmakers commented on TAP5-64: - Separate jar is what I'd expect; you don't want to force portlet.jar upon everybody. Out of the box, as in documented and provided on tapestry.apache.org just like all tap5 jars. (I'm still maintaining a tap4-based portlet app and I would love to migrate to tap5.) 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 Assignee: François Facon 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 was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13789439#comment-13789439 ] Thiago H. de Paula Figueiredo commented on TAP5-64: --- Hello, Pieter! If tapestry5-portlet is working and if it had its JARs in the Maven Central Respository, would you be satisfied? As I said in the message above, we cannot have too much stuff under the Tapestry project itself because otherwise we wouldn't have the time to support all that. Cheers! 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 Assignee: François Facon 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 was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13789482#comment-13789482 ] Pieter Schoenmakers commented on TAP5-64: - Inclusion on tapestry.apache.org is like a seal of approval. It provides trust. Provision from somewhere else lacks the seal. It must earn the trust all by itself. On the other hand, portlet support from tapestry.apache.org reflects good on tapestry itself. If I were running tapestry, I'd want portlet support in there. All other serious UI frameworks support portlets :-) But, we're talking hypotheses here. The attached jars would need to be brought up to par with the latest tap5 before being able to be considered for inclusion. 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 Assignee: François Facon 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 was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13789511#comment-13789511 ] Thiago H. de Paula Figueiredo commented on TAP5-64: --- What if the Tapestry documentation itself had a Recommended third-party modules section? For example, tapestry-security, the integration with Apache Shiro, isn't part of the Tapestry project itself but it's written by a committer of both Tapestry and Shiro and it's widely trusted. Latest released Tapestry version is 5.3.6 and tapestry5-portlet says it supports them. 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 Assignee: François Facon 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 was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13789553#comment-13789553 ] Thiago H. de Paula Figueiredo commented on TAP5-64: --- In addition, Tapestry *does* support portlets, but by using a thirdy-party module. 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 Assignee: François Facon 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 was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13789616#comment-13789616 ] François Facon commented on TAP5-64: I'm still working on this jira. this module is already in production and working correctly for 5.2.6, 5.3.7, 5.4.AlphaXX. the build process and testing integration with Pluto works well with Maven. The gradle build is ok but I have not managed to use Tomee Pluto and Arquilian in a gradle build. Any technical feedback is welcome 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 Assignee: François Facon 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 was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13265987#comment-13265987 ] François Facon commented on TAP5-64: Like Felix Scheffer (http://code.google.com/p/tapestry5-portlet-support/ for more details), we have updated the dependencies of this library to use Tapestry 5.2.6. This library also support: - portlet event processing (JSR 286) - serving ajax request as portlet resource (event name that start with serve or components declared in the PortletResourceResponseIdentifier service) - support MARKUP_HEAD_ELEMENT - rework on IdAllocator to avoid conflict for generated id when there is more than on tapestry portlet in a page. - use of Apache Pluto to ease the test Code is available at https://github.com/got5/tapestry5-portlet. If you want to see it in action, you just need to: - Download the sources - Go to the repository directory - Run mvn jetty:run - Open your browser to http://localhost:8080/tapestry5-portlet/portal/Index This bridge is available also in snapshot version for Tapestry 5.3.3. To come : documentations and gradle tasks to prepare a clean move to main Tapestry project (Targeted version 5.4) 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 Assignee: François Facon 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
[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-tabpanelfocusedCommentId=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
[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-tabpanelfocusedCommentId=13084012#comment-13084012 ] François Facon commented on TAP5-64: we have an ongoing study on this subject based on Makus work. 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. For more information on JIRA, see: http://www.atlassian.com/software/jira
[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-tabpanelfocusedCommentId=13083570#comment-13083570 ] Massimo Lusetti commented on TAP5-64: - Does this still current and with interested? 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. For more information on JIRA, see: http://www.atlassian.com/software/jira
[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-tabpanelfocusedCommentId=13083658#comment-13083658 ] postmaster@cumquat commented on TAP5-64: Beste afzender, Dit e-mailadres van Cumquat is niet langer meer in gebruik. U kunt contact opnemen met Cumquat via een van de onderstaande e-mailadressen: - project.off...@cumquat.nl voor projectgerelateerde onderwerpen - sa...@cumquat.nl voor commerciële onderwerpen - i...@cumquat.nl voor algemene onderwerpen Dank u wel. Dear sender, This e-mail account of Cumquat is no longer is use. Please contact Cumquat by using one of the e-mail accounts below: - project.off...@cumquat.nl for project related issues - sa...@cumquat.nl for sales questions - i...@cumquat.nl for general questions Thank you. Cumquat Information Technology B.V. De Dreef 19 3706 BR ZEIST t +31 (0)30 6940 490 f +31 (0)30 6940 499 i www.cumquat.nl 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. For more information on JIRA, see: http://www.atlassian.com/software/jira
[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-tabpanelfocusedCommentId=12838565#action_12838565 ] Markus Feindler commented on TAP5-64: - Hey, I have extended the code of Tran Le Xuan and Kristina B. Taylor. XHR Requests and Resource Serving has been implemented. Check details on my google code project: http://code.google.com/p/tapestry5portlet/ 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. - You can reply to this email to add a comment to the issue online.
[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-tabpanelfocusedCommentId=12832013#action_12832013 ] Marcus commented on TAP5-64: Due the new portal features in JSR-286 (events, resource serving (ajax), filters, policy, public render parameters), don't you think that Portlet2 deserves a separate version of Tapestry? There is a gap in this area. 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. - You can reply to this email to add a comment to the issue online.
