• Improved ajax processing (faster load times)
• PRP - Public render parameter processing in the bridge
• Seam exception handling in pages.xml
• better error handling for JSF and Richfaces portlets (this includes ViewExpiredException)
• Also fixed some bugs in archetypes to work fully with JBoss Tools (as seen in the video)


• PortalIdentity is now built in Seam component
  <security:portal-identity method="#{authenticator.authenticate}"></security:portal-identity>


• Script Renderer can be enabled by intit parameter in web.xml:
  

  <context-param>
      <param-name>org.jboss.portletbridge.WRAP_SCRIPTS</param-name>
      <param-value>true</param-value>
  </context-param>

This video shows how to deploy a Seam portlet using JBoss Tools to the all new GateIn portal. I also show need-to-know tips for migrating from the 1.0 bridge to 2.0.

JBoss Portlet Bridge Episode 4: Running 2.0 on GateIn from Wesley Hales on Vimeo.

• Update your status
• Get messages that are sent directly to you (e.g. @prabhatjha in my case)
• Get list of folks who you are following and get their latest status. List is sortable.

JBoss Portlet Bridge - Lesson 3: Seam and Portlet 2.0 Eventing from Wesley Hales For a full description of what’s new in this version, mandatory configuration parameters, and instructions on using portlet 2.0 coordination features, see the Reference Guide.  

Mark Little, Sr. Director of Engineering, Middleware at Red Hat The eXo portal has some impressive functionality in terms of ease of use, UI flexibility and straightforward management administration; JBoss.org's current portal project has a robust engine, performance and security features, combined this collaboration project will help drive portal capabilities forward

Benjamin Mestrallet, CEO eXo Platform Open source software has delivered substantial returns on investment for organizations and we have the opportunity to deliver that same value within the portals space

• Julien Viet commented on the history (worth a read)
  
• http://exoplatform.com/portal/public/website/aboutUS/eXoJBossPartnership
• http://www.jboye.com/blogpost/exo-portal-and-jboss-portal-join-forces/
• http://blog.internetnews.com/skerner/2009/06/red-hat-jboss-gets-exo-portal.html
• http://www.reuters.com/article/pressRelease/idUS115834+10-Jun-2009+BW20090610
  

• Integration of JBoss Portal and SSO server on same host (HTTP protocol is used).
• Integration of JBoss Portal and SSO server on same host. Secure communication is used between JBoss Portal agent and SSO framework (HTTPS protocol is used).
• Integration of SSO server and more JBoss Portal instances deployed on multiple hosts
• Integration of JBoss Portal, SSO server and sample thirdparty web application.
• Integration of JBoss Portal and SSO server deployed on different hosts. SSO server is configured for authentication against portal database.
  

JBoss Portlet Bridge - Lesson 2: Portlet 1.0 Advanced Seam and RichFaces from Wesley Hales on Vimeo.

To show off some new features in the CR2 release, I threw together a simple chat-client and chat-room set of portlets using Richfaces poll and Seam stateful session beans.

This screencast shows how to use the new PortletScope annotation along with the revised SSO/PortalIdentity component.

Source code for this tutorial:
http://anonsvn.jboss.org/repos/portletbridge/tags/1.0.0.CR2/examples/seam/bridgechat/

See the reference guide for more info: http://www.jboss.org/files/portletbridge/docs/1.0.0.CR2/en/html_single/index.html

• The RichFaces file upload rich:fileUpload component is working. The component currently only works with the param createTempFiles set to false in your web.xml. Also, you must check for the response type is of type RenderResponse. See the paint() method for an example.


• The PortalIdentity bridgelet which provides SSO between your Seam portlet and JBoss Portal is now working with the current Seam 2.1.x Identity model. See here for details.
  


• The PortalResourceBuilder bridgelet received a noteworthy upgrade and now works (should work) in all browsers. This component is for portal pages that contain 2 or more RichFaces components in seperate portlet windows. It namespaces the auto generated RF javascript and loads it only once for each component.
  


• Better docs, scalability upgrades, markup validation fix, and many other bug fixes went into this release. See the release notes for more info.
  

• Clean Separation between Security Logic and Application Logic
• Flexibility to apply Security Logic to arbitrary Runtime information, and not just Role based access control
  
• Runtime Management of Security Policy
• A user friendly Developer API

• A standards compliant XACML server. More Spec Info.
  
• Runtime modification of Security rules without requiring any system restarts
• Ability to create complex security rules taking into account useful contextual data like Identity, Roles, Arbitrary Request Parameters, Date/Time based rules, IP Address based Rules etc
• A Developer friendly component oriented API to develop custom Security GUI to manage Policies. Developers do not need any familiarity with the low-level complex XACML XML hell.
• A common Security Manager for all your Portlet applications, without having to write/maintain a separate Security subsystem for each Portlet application being aggregated

• SVN : Preview Release
• Documentation: Reference Guide
• Forum: Design Discussion
  

• API/SPI separation that should enable easier adoption of different identity managers or identity stores in the future.
• Notion of Identities and Groups (organizations) with flexible relationships between them
  
• Concept of a Role that is a typed connection between Identity and Group object. This enables to map sentence like "John is the Manager of XX Team" to " John ( Identity ) is the Manager ( RoleType ) of XX Team ( Group )"
  
• Abstract attributes and credentials

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:

<dependency>
   <groupId>org.jboss.portletbridge.extensions.richfaces</groupId>
   <artifactId>PortalResourceBuilder</artifactId>
   <version>1.0.0.B6</version>
</dependency>

• Peter Johnson for his forum activity in the issue/Jira category.
• Luca Stancapiano for the admin portlet internationalization and the Who's online portlet in the new feature category .
• Dan Krieger in the bug fix category.

• Why portals still matter to the enterprise
• How innovative companies have leveraged portals and content solutions to drive business results
• What benefits can be reaped by partnering with a team of independent, open source providers