The release is a fully compliant implementation of the Portlet 2 (JSR286) specification, which was released yesterday.
JBoss Portlet Container 2.0 comes with a lightweight portal based on JSP tags and comes bundled with a few demonstration portlets. The goal of that lightweight portal is to provide developers with an easy way to showcase and test their portlet applications. It should work well with other JSP taglibs and templating frameworks.
It provides advanced functionalities:
- Administration application which provides an overview of the deployed applications / portlets / filters and management of their life cycle. Failed portlets or filters can be restarted or stopped when needed.
- Event debugger which should prove very userful to understand complex event interactions.
- Event flood detection to prevent events from running wild.
- Management of life cycle dependencies between portlet filters and portlet container: if a portlet filter fails and is stopped then all the portlet containers dependent on that filter will also be stopped (otherwise it would obviously result in an incorrect application).
- Optimized event payload marshalling: when an event with an object payload is fired from application A to application B, the event will be unmarshalled/marshalled between the two applications classloaders (otherwise it would result in a class cast exception) unless the event class is shared at the server level, in which case the event can be safely transported across application borders.
The next major release of our mainstream portal product JBoss Portal 2.7 will bundle the JBoss Portlet Container.
You can download the release from our project download page.
5 comments:
Is there any schedule on getting WSRP with the Portlet Container rather than requiring the full Portal to be able to expose portlets via WSRP?
We have plans to extract WSRP from Portal. However, we are currently focusing on getting Portal 2.7 (which will use JBoss Portlet Container 2.0) out as soon as possible.
Congrats to Julien and the JBoss Portal team! What are your plans for implementing the optional features of JSR-286 such as portlet-managed modes and escapeXml/renderHeaders runtime container options?
Hi Craig,
we do implement escapeXml option.
the renderHeaders option is not on our roadmap as our container is aligned with the WSRP model and performs buffering of the portlet response anyway.
we need to implement the portlet managed mode as part of the runtime metadata exposed by the portlet container to the portal.
jboss portlet container can run on weblogic or webshpere？
Post a Comment