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

Release Highlights

• Many fixes to how resource urls are generated for RichFaces 4 portlets which resolves problems such as with icons for rich:tree
  

• Resolve exceptions that occurred when a new skin was chosen in the RichFaces 4 showcase portlet
  
• Update to RichFaces 4.3.0.M3, which includes a fix for rich:extendedDataTable not being correctly sized when a containing element was set to width=100%
  
• Fix a threading issue for the variable holding the ELContext which caused exceptions when executing multiple requests at once. Thanks to Alex K from the community for pointing that one out and providing a fix!
  
• Now support JSF2 portlets using CDI!
  

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

Enabling CDI for your portlet

To enable CDI in a JSF2 portlet we've created a separate integration library that you'll need to include in your archive.  The Maven dependency is:

<dependency>
    <groupId>org.gatein</groupId>
    <artifactId>cdi-portlet-integration</artifactId>
    <version>1.0.0.Alpha2</version>
</dependency>

All details of how to add the Portlet Filter for CDI to your portlet.xml and what restrictions there may be on vanilla CDI can be found in our docs.

It's important to note that this library is for use with CDI 1.0 containers.

Maven coordinates:

For a JSF2 only portlet:

<dependency>
    <groupId>org.jboss.portletbridge</groupId>
    <artifactId>portletbridge-api</artifactId>
    <version>3.2.0.Alpha1</version>
</dependency>
<dependency>
    <groupId>org.jboss.portletbridge</groupId>
    <artifactId>portletbridge-impl</artifactId>
    <version>3.2.0.Alpha1</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.Alpha1</version>
    <scope>runtime</scope>
</dependency>

Keeping up with the latest

One of the best ways to hear about the latest releases and changes with JBoss 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 JBoss Portlet Bridge, please get in touch.