Skip navigation
1 2 Previous Next

Portlet Bridge

29 posts

We're pleased to announce that 3.1.0.Final of Portlet Bridge is now available!

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

 

This release brings together the combined work of the Portlet Bridge and RichFaces teams to bring RichFaces support to portlets with more component support than was available in the past.  I'd like to thank Alexandre Mendonça, Brian Leathem (RichFaces Lead), and Lukáš Fryč for all their assistance in making this happen.

Maven coordinates:

For a JSF2 only portlet:

 

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

 

RichFaces 4 Portlet

In this release we added a new RichFaces 4 example that has a form, with ajax submission and validation, with an extended data table below it to show all the submitted data.  What's also cool is that the table supports sorting on single or multiple columns.  We hope this example provides a good way to see RichFaces 4 in action in a portlet.

Archetypes

We also updated the JSF 2 archetype, as it had been neglected for far too long, to bring it into line with what is really essential for a JSF 2 application in a portlet to define.

 

A new archetype was added for RichFaces 4 to make it even easier to get up and running in a hurry!

Moving Forward

Fixing any issues the community finds will continue to be a focus, so keep trying out Portlet Bridge and letting us know how it can be improved, but we'll also look to begin development on some new features.  Areas we're looking at include support for CDI, Seam 2.3 and Spring.  What support for each of these entails we don't know yet, but if you'd like to find out why not join us in making it happen!  All details on future release plans can be found here.

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 that 3.1.0.CR1 of Portlet Bridge is now available!

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.1.0.CR1</version>
</dependency>
<dependency>
    <groupId>org.jboss.portletbridge</groupId>
    <artifactId>portletbridge-impl</artifactId>
    <version>3.1.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.1.0.CR1</version>
    <scope>runtime</scope>
</dependency>

 

Update to RichFaces 4.2.3.Final

RichFaces 4.2.3.Final was released a week ago and we've now updated our portlet showcase to take advantage!

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 that 3.1.0.Beta3 of Portlet Bridge is now available!

Maven coordinates:

For a JSF2 only portlet:

 

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

 

Update to RichFaces 4.2.3.CR1

RichFaces 4.2.3.CR1 was released earlier today, thanks Brian! You can check out all the details here, as they include several important fixes for RichFaces 4 in a portlet!

WSRP support for RichFaces 4

In this release we've also improved the support of RichFaces 4 components when a portlet is being used over WSRP, with 76 out of 77 components now supported!

 

I'd like to thank Brian Leathem and Lukas Fryc for their continued support in getting to the root of any issues that may arise with using RichFaces 4 in portlets, without their support Portlet Bridge would not have almost complete RichFaces4 component support this soon!

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 that 3.1.0.Beta2 of Portlet Bridge is now available!

Maven coordinates:

For a JSF2 only portlet:

 

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

 

Depchain POMs

As part of this release we split out any RichFaces 4 specific code into it's own module to enable cleaner separation of concerns in the code.  So to make things simpler now that we have three separate dependencies if you're writing a RichFaces 4 portlet we've also introduced a depchain for JSF2 and RichFaces 4 dependencies.

 

For a JSF2 portlet the depchain you need is:

 

<dependency>
    <groupId>org.jboss.portletbridge</groupId>
    <artifactId>jsf2-depchain</artifactId>
    <version>3.1.0.Beta2</version>
</dependency>

 

For a RichFaces 4 portlet the depchain you need is:

 

<dependency>
    <groupId>org.jboss.portletbridge</groupId>
    <artifactId>richfaces4-depchain</artifactId>
    <version>3.1.0.Beta2</version>
</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.

We're pleased to announce that 3.1.0.Beta1 of JBoss Portlet Bridge is now available!

Maven coordinates:

<dependency>

    <groupId>org.jboss.portletbridge</groupId>

    <artifactId>portletbridge-api</artifactId>

    <version>3.1.0.Beta1</version>

</dependency>

<dependency>

    <groupId>org.jboss.portletbridge</groupId>

    <artifactId>portletbridge-impl</artifactId>

    <version>3.1.0.Beta1</version>

    <scope>runtime</scope>

</dependency>

 

RichFaces 4 fileUpload

This release brings support for fileUpload in RichFaces! There is still a minor bug within RichFaces 4.2.2 that prevents it working in portlets, but it is resolved in the current 4.3 work. Check out RF-12273 for details on the fix, as it can easily be applied to 4.2.2.Final.

Now all RichFaces 4.2.2.Final components are supported within non WSRP JSF portlets!

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 that 3.1.0.Alpha2 of JBoss Portlet Bridge is now available!

Maven coordinates:

<dependency>

    <groupId>org.jboss.portletbridge</groupId>

    <artifactId>portletbridge-api</artifactId>

    <version>3.1.0.Alpha2</version>

</dependency>

<dependency>

    <groupId>org.jboss.portletbridge</groupId>

    <artifactId>portletbridge-impl</artifactId>

    <version>3.1.0.Alpha2</version>

    <scope>runtime</scope>

</dependency>

 

Minor Fixes

This release focused on fixing a few minor issues, along with a new feature that will set style and script resources within the <head> section of your portlet into the <head> section of the portal page.

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 extremely pleased to announce that 3.1.0.Alpha1 of JBoss Portlet Bridge is now available!

 

This release brings support for 76 RichFaces 4.2.2 Components in a portlet!

Maven coordinates:

<dependency>

    <groupId>org.jboss.portletbridge</groupId>

    <artifactId>portletbridge-api</artifactId>

    <version>3.1.0.Alpha1</version>

</dependency>

<dependency>

    <groupId>org.jboss.portletbridge</groupId>

    <artifactId>portletbridge-impl</artifactId>

    <version>3.1.0.Alpha1</version>

    <scope>runtime</scope>

</dependency>

 

RichFaces 4 Components

This release brings support for 76 RichFaces components in a portlet!  For a full list of all the supported portlets please check out: RichFaces 4.2.2.Final Component Compatibility

 

For the next release we intend to support all RichFaces components in 4.2.2, and add support for these components over WSRP.

 

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 3.0.0.Final of JBoss Portlet Bridge is now available!

 

This release has been a long time in the making, but we now have JSF 2 support for portlets.  The next steps are to polish JSF 2 support with more complete automated tests while also adding support for RichFaces 4 components.

Maven coordinates:

<dependency>

    <groupId>org.jboss.portletbridge</groupId>

    <artifactId>portletbridge-api</artifactId>

    <version>3.0.0.Final</version>

</dependency>

<dependency>

    <groupId>org.jboss.portletbridge</groupId>

    <artifactId>portletbridge-impl</artifactId>

    <version>3.0.0.Final</version>

    <scope>runtime</scope>

</dependency>

 

Documentation

The documentation for 3.0.0.Final can be found here.

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 CR1 in the 3.0 series of JBoss Portlet Bridge is now available! The plan is to release Final in about a week, to allow for documentation to be written in support of the Final release.

 

Maven coordinates:

<dependency>

    <groupId>org.jboss.portletbridge</groupId>

    <artifactId>portletbridge-api</artifactId>

    <version>3.0.0.CR1</version>

</dependency>

<dependency>

    <groupId>org.jboss.portletbridge</groupId>

    <artifactId>portletbridge-impl</artifactId>

    <version>3.0.0.CR1</version>

    <scope>runtime</scope>

</dependency>

 

TCK

This release now passes the TCK for Portlet Bridges with JSF, which is a huge achievement that we're very proud of.

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 JBoss Portlet Bridge 2.3.1.Final is now available.  This release fixes some important resource URL handling that was broken in 2.3.0.Final.

 

Maven coordinates:

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

 

Here is a list of the issues that have been resolved for this release:

  • [PBR-287] - Clustering: BridgeRequestScope can end up with an uninitialized beans field on unmarshalling
  • [PBR-320] - response.createResourceURL() broken from PBR-307
  • [PBR-321] - The fix of PBR-276 steal the messages from ajax-resource-requests
  • [PBR-323] - Docs: Command for generating archetypes does not work
  • [PBR-324] - Docs: RENDER_POLICY configuration is misspelled
  • [PBR-325] - Docs: Portlet name missing in the code for NONE LoadStyleStrategy
  • [PBR-361] - Backport fix in EPP Branch for Resource Handling in RichFaces
  • [PBR-366] - ViewExpiredException caused by Session expiration being masked by NPE

 

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 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.

Ken Finnigan

3.0.0.Beta2 Released

Posted by Ken Finnigan Apr 12, 2012

Well it took a little longer than expected, but we've now released JBoss Portlet Bridge 3.0.0.Beta2!

 

This release marks the commemcement of more frequent release cycles, typically about 2 weeks.  The current release schedule is kept up to date, so if you want to find out about future releases, check it out.

 

This release incorporates a great deal of API changes to standardize amongst everyone from the JSR 329 EG, with a view to a future JSR that supports JSF 2.  This release also focuses on JSF 2 support only, a future release will work to incorporate RichFaces 4 and Seam 2.3.

 

So head over to the Downloads page, or add the following Maven coordinates:

 

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

 

Ken

As the development of JBoss Portlet Bridge 3.x ramps up again, you may have noticed some changes going on in the community space.

 

There is now a dedicated community space to discuss development of Portlet Bridge at Portlet Bridge Development.  There are already some articles present around how to contribute to the project, what our development workflow is, and our tentative roadmap plans for the coming months!

 

We're very open and eager to have anyone help out that wishes to, in any way that they are able!

 

The tentative roadmap is more aggressive than the past, but I believe it's time to be as agile as possible in the project releases.  I'd rather release more often, with less changes between each, to garner community feedback as soon as possible about our direction and progress.

 

If you, the community, have any other ideas about how JBoss Portlet Bridge could improve as a project, don't hesitate to come by the development forums to express your views!

 

Thanks

Ken Finnigan

JBoss Portlet Bridge Lead