Skip navigation
2012

We're pleased to announce Beta4 in the 3.0 series of JBoss Portlet Bridge is now available, which will be the last Beta before CR1.

 

Maven coordinates:

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

 

Arquillian Graphene and Drone

This release modifed the Arquillian tests to use Graphene and Drone for controlling the Browser within the test, which will make it easier and quicker to introduce additional tests each release.

JSF 2 Exception Handling

We've introduced a JSF 2 ExceptionHandler implementation for portlets that will redirect to the error page you've specified in web.xml for any Throwable's that match.

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.

We're pleased to announce Beta3 in the 3.0 series of JBoss Portlet Bridge is now available.

 

Maven coordinates:

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

 

Arquillian testsuite

The biggest change for this release is the introduction of an automated test suite utilizing Arquillian that enables us to test JSF 2 portlets easily and quickly.  At the moment there are portal containers for GateIn on AS7 and Pluto on Jetty, but in the future we will look to expand that list.  You can check out the container integration for GateIn and Pluto on GitHub, and see how they are used to test portlets with the Portlet Bridge testsuite such as in this example.

 

In future releases we plan to introduce more test portlets to ensure that the entire JSF 2 functionality is always tested in a portlet environment on each release.

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.