Wesley Hales, lead JBoss Portal UI Engineer has announced the beta 6 release of JBoss Portlet Bridge --
Only a month after beta 5, we are releasing beta 6 with some nice
enhancements and bug fixes. I'm pretty sure this will be the last beta
release for the 1.0 version. As most of you know, the JBoss Portlet
Bridge is a little different than most implementations. We are
integrating Seam and RichFaces, so even though the JSF part of the
bridge may be running at a GA level (and the spec being final), the
RichFaces and Seam integration still has some work left to be done and
that may be at a candidate or beta level. As always, let us know what
you think and join us on the forums.
Along with the small fixes, here is what's new:
dependencies are no more for a normal JSF portlet. Previously you
needed the RichFaces jars on your classpath to use the bridge. This was
mostly due to early development integration of ajax in the 301 bridge
which needed to be refactored.I created a new Bridgelet called PortalResourceBuilder.
RichFaces does not account for multiple components on the same portal
page by default. This Bridgelet renders all RichFaces component
include this jar on your classpath or add the following dependency to your pom.xml:
is now an automatic propagation of Locales. Any
<supported-locales/> defined in portlet.xml will be automatically
added to your JSF application running inside the portlet. Currently
this is only available for JBoss Portal in the 1.0 bridge due to
getSupportedLocales() not being in the spec. This should be fully
available to all portlet containers in the 2.0 bridge.
View the reference guide
for more information.
See Also --