We're pleased to announce that 3.2.0.CR1 of Portlet Bridge is now available!

Release Highlights

• Upgrade to RichFaces 4.3.1.Final
• Upgrade to Mojarra 2.1.19
• Fix a bug in portlet URL generation when the JSF View uses a different mapping to that of the view being linked. For instance a View using suffix mapping would generate an incorrect portlet url for a prefix mapped View.
• Resolve a memory leak issue for @RequestScoped, @ViewScoped and @SessionScoped JSF Managed Beans running in AS7. For @ViewScoped memory leaks to be fixed, Mojarra 2.1.19 or greater is also required.

Full details of all the changes can be found in the release notes

Maven coordinates:

For a JSF2 only portlet:

<dependency>
    <groupId>org.jboss.portletbridge</groupId>
    <artifactId>portletbridge-api</artifactId>
    <version>3.2.0.CR1</version>
</dependency>
<dependency>
    <groupId>org.jboss.portletbridge</groupId>
    <artifactId>portletbridge-impl</artifactId>
    <version>3.2.0.CR1</version>
    <scope>runtime</scope>
</dependency>

For a RichFaces 4 portlet you need the above as well as:

<dependency>
    <groupId>org.jboss.portletbridge</groupId>
    <artifactId>portletbridge-extension-richfaces</artifactId>
    <version>3.2.0.CR1</version>
    <scope>runtime</scope>
</dependency>

Keeping up with the latest

One of the best ways to hear about the latest releases and changes with Portlet Bridge is to follow us on Twitter (@portletbridge).

Don't be a stranger

As always, if you have any questions about or issues with Portlet Bridge, please get in touch.