The Portlet-Utils have been revived and we've added a first version of a portletregistry that enables portlet developers to register portlets based on a "servicename" and create Action/Render/Resource URLs in any given time for any registered portlet based on the servicename that has been used during the registration.

Portlets can also register for multiple servicenames. This decouples the concrete portletid from the service that a portlet offers.

The implementation is currently EJB3 based with a DB backend that is used via JPA for persisting the registrations. The implementation also can't handle multiple registrations for one servicename at the moment. The servicename always returns the last saved value. An admin interface to register for example portlets that you can't or won't enhance with a registration functionality is yet missing too, but we'll start to implement in the next step. See in the docs directory for more informations on how to use the portletregistry.

The registry is currently able to generate URLs for Liferay based portals, but the project has been designed to support multiple implementations for other portal servers. You basically just need to provide an implementation for the portletURL interface. You can have a look at our liferay based implementation to see how easy it is.

The project is work in progress. Feel free to provide ideas, bugreports or code. The license is GPLV3.