tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From François Facon (JIRA) <j...@apache.org>
Subject [jira] [Commented] (TAP5-64) Support Java Portlet Specification V2 - JSR-286
Date Tue, 01 May 2012 19:16:50 GMT

    [ https://issues.apache.org/jira/browse/TAP5-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13265987#comment-13265987

François Facon commented on TAP5-64:

Like Felix Scheffer
(http://code.google.com/p/tapestry5-portlet-support/ for more
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
- 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


View raw message