This is not a tag line!
portal
Improving deployment of WSRP-related artifacts in GateIn
Mar 9th
As you may know, I am working on WSRP for GateIn. One problem I faced until today in my daily development was that deploying a new version of the WSRP module for testing required re-building GateIn completely, which takes quite a bit of time and has the side effect of also destroying any persisted data. This, in turn, resulted in even more wasted time spent on configuring GateIn so that I could perform my tests (configuring consumers, adding remote portlets to pages, etc).
I decided that I could make that process faster by just replacing the WSRP artifacts in an already built version of GateIn if there hadn’t been any API change in the WSRP module. I present the following script to that effect:
# extract most recent version of WSRP module: only check the first 5 lines of maven-metadata-local.xml and extract value from <version> tag export CURRENT_WSRP=`sed -n -e '5 s/.*<version>\(.*\)<\/version>.*/\1/p' $HOME/.m2/repository/org/gatein/wsrp/wsrp-common/maven-metadata-local.xml` echo Current WSRP version: \'$CURRENT_WSRP\' # extract which WSRP libs are currently needed by GateIn and replace them with a fresh version from local repository for lib in `ls $GATEIN_EAR_HOME/lib/wsrp* | sed -n 's/.*\/\(.*\)-'$CURRENT_WSRP'.jar/\1/p'` do echo Copying $lib-$CURRENT_WSRP.jar to $GATEIN_EAR_HOME/lib/ cp $HOME/.m2/repository/org/gatein/wsrp/$lib/$CURRENT_WSRP/$lib-$CURRENT_WSRP.jar $GATEIN_EAR_HOME/lib/ done # deal with producer and admin GUI WARs separately as they are put elsewhere and without version name for war in `ls $GATEIN_EAR_HOME/wsrp* | sed -n 's/.*\/\(.*\).war/\1/p'` do echo Copying $war-$CURRENT_WSRP.war to $GATEIN_EAR_HOME/$war.war cp $HOME/.m2/repository/org/gatein/wsrp/$war/$CURRENT_WSRP/$war-$CURRENT_WSRP.war $GATEIN_EAR_HOME/$war.war done
Note that this script expects that you have a $GATEIN_EAR_HOME variable set, pointing to location of your GateIn EAR. Easy enough (though I had to freshen up my sed-fu ^_^).
# extract most recent version of WSRP module from existing files CURRENT_WSRP=`ls $GATEIN_EAR_HOME/lib/wsrp* | sed -n '1 s/.*\/.*-\([0-9]\.[0-9].[0-9]-.*-.*\).jar/\1/p'`
Might be faster that way…
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:
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>
