With the last version of the portal that is going to be released in September, it’s possible to deploy GWT application within eXo Portal. They can also be deployed as widget (on the left panel and the background of the WebOS)
Once again, standards compliance pays off. As you know, at eXo we have a long story with standards compliance. Having a portlet API compliant portlet container, saved my day recently.
I was wondering how difficult it would be to run a RichFaces application in eXo. I was able to easily grab and build the source code of the JBoss RichFaces Demo Portlet.
A couple of xml changes later, I had it running quite nicely under eXo Portal. Take a peek at this video :
OK, that’s no more than what you can see elsewhere. But it is always good to know that our technology plays well with others.
The demo runs with the help of JBoss Portlet Bridge which is an early implementation of the JSR 301 : Portlet Bridge for JSF.
Even if only in 1.0.0 beta3, it looks very promising. Congratulations to the team!
At eXo, we will closely follow your progress and make sure that the bridge keeps playing well in eXo Portal.
Last week, we gave a 3-days training on eXo Portal at La cantine.
It’s a very unique collaborative place in Paris city center, dedicated to co-working and innovation. We would like to thank the staff for their warm welcome and helpfull care.
The training covered eXo Portal concepts, administration and configuration. We also had one full day dedicated to discovering latest JSR 286 features in quick development exercices.
All went in a studious but relaxed atmosphere. To get a better idea, have a look at the following excerpt video :
eXo team has been working hard to build a full featured collaboration suite that sits on top of eXo Portal. CS 1.0 applications are rich portlets that run on top of eXo Portal 2.0 or eXo WebOS 1.0.
This long awaited release is the new version of the first product the eXo team ever launched back to the old JSR 168 times (November 2004). This brand new version includes the new Portlet API 2.0 (JSR 286) as well as the implementation of the WSRP 2 pre released specification.
eXo PC is bundled along with a lightweight test portal and a number of demo portlets for testing purpose.
This packaged is great for Independent Software Vendors (ISV) that would like to add portlet features to their applications.
Here are the list of the most important features:
Portlet Container
- Full compliance with the Portlet API 2.0 final specification - JSR 286 (100% TCK tests passed)
- PC plugin mechanism
- Extensible Portal framework
- New portlet apptiocation deployment descriptor
- New API interfaces
- Container Runtime options support
- Resource ID support
- Annotated methods support
- Event processing
- PortletURLGenerationListener
- JAXB type validation for event payload
- Cache levels for resource URLs
- Predefined container events
- Portlet filter support
- Validation cache and ETAG support
- New tags in tag library
- Include/forward processing changes
- Public render parameters
- HTTP headers/response full control for processResource()
- AJAX-compliant URL generation
WSRP
- Full compliance with the WSRP 2 plugin to the WSRP 2 PR03 specification
- WSRP plugins for the PC (WSRP 1.0 and WSRP 2.0 plugins)
- WSRP administrative portlets built in into plugins
- WSRP starter mechanism
- AXIS 1.4 based code
- Three step protocol
- Resource serving
- Event handling
- Navigational parameters
- JAXB event binding
- State distribution
Here i a picture of the new eXo PC 2.0 architecture built on top of a plugin design that allows portal to handle local or remote portlets transparently…bye bye the old JSR168ProxyPortlet!