This is not a tag line!
jboss
GateIn 3.0 CR1 released!
Feb 18th
Where have I been? Well, mostly working towards releasing GateIn (we just released CR1, by the way, go grab it, put it through the motions and let us know if you find any issues).
We had a nice face to face meeting in Charmey, Switzerland with some of the eXo guys. It was nice to see my co-workers and meet new ones. Lots of good discussions. We even found a way to fit in some fun, which is always good to bind teams. Oh, and we did, of course, get to eat various melted cheese dishes and you can’t really go wrong with that! 
GateIn 3.0.0 Beta 2 released!
Oct 21st
As some of you may know, JBoss and eXo have decided to merge their portal efforts in an attempt to create the best open-source portal framework out there. This new, best-of-breed portal project is called GateIn.
Integrating both code bases has taken (and still does) a lot of effort from both teams. This has translated in some long hours and little sleep but we’ve just released a new beta version for you to try and enjoy! Apart from lots of improvements and fixes, the big news is, of course, that we now provide the complete source code! Read more about it on the official GateIn blog.
Of course, we’re not done yet so keep watching the blog. You can also follow GateIn on Twitter.
JBoss Portal 2.7.2 is released!
Mar 13th
It’s been a couple of really busy weeks at work as we have been ironing out the last couple of issues that we wanted to solve before unleashing JBoss Portal 2.7.2 unto the world!
It’s finally done and 2.6.8 should follow suite soon. I can now re-gather my thoughts and energy towards 2.8 and beyond!
Read more about the release from our fearless leader on the official JBoss Portal blog.
JBoss Portal 2.6 is released!
Jul 2nd
Lots of work over the last ten months and there it is: JBoss Portal 2.6.0.GA has been released today! In particular, this includes my work on WSRP which has been significantly beefed-up since our first, base-level support introduced in 2.4. We now support the complete specification (albeit at different profile levels) including the ability to clone, personalize and manage remote portlets and their lifecycle.
Some coverage:
First post on JBoss Portal’s blog
Jun 29th
I have finally posted a post on JBoss Portal’s developer blog. It’s a short but sweet opinion piece about how iPhone’s support for full-fledged web browsing and Apple’s SDK stance could be an opportunity for Portal developers.
In other news, we (as in the Portal team) have been busy working on the GA release of JBoss Portal 2.6. This work should bear fruits real soon now and it has lots of new, cool features along with improvements all over. Watch JBoss Portal’s blog for an announcement soon.
JBoss Portal 2.6 is in alpha…
Feb 9th
… and ready for your consumption! Most notably, as far as I am concerned, it includes a near-complete implementation of the WSRP 1.0 specification so please give it a try and let me know if you break anything so that I can correct any problem!
JBoss Portal 2.4 Alpha released!
May 16th
It’s been a couple of busy months and it’s been particularly busy the last couple of weeks but we have released an alpha of the upcoming version of JBoss Portal which, among other numerous improvements, include what I have been working on specifically: support for WSRP!
Oh, yeah, if you want to learn all about it be sure to attend JBoss World in Las Vegas where I’ll be presenting a session on WSRP and JBoss Portal. 
Activating dev mode in JBoss Portal
May 16th
By default, portlet errors are swallowed up by JBoss Portal but you can change that so that errors such as portlet unavailability, etc… are displayed. To achieve such result, you should modify the config.xml file in portal-core.sar/conf so that the properties to show/hide the appropriate errors are to your liking:
<properties>
<!-- When a window has restrictedaccess : show or hide values are permitted -->
<entry key="core.render.window_access_denied">show</entry>
<!-- When a window is unavailable : show or hide values are permitted -->
<entry key="core.render.window_unavailable">show</entry>
<!-- When a window produces an error : show or hide values are permitted -->
<entry key="core.render.window_error">show</entry>
<!-- When a window is not found : show or hide values are permitted -->
<entry key="core.render.window_not_found">show</entry>
</properties>
