[Hypercontent-developer] HyperContent 2.0b4 now available

[Alex V. <av...@co...>]

Hello all,
	I have just posted a link to the fourth beta release of HC2 on the 
HyperContent home page.  This release contains a number of bug fixes 
based on our initial production migrations at Columbia, and adds 
support for recursive navigation/site-map generation for doctypes with 
** patterns.  But most importantly, it adds hooks for integration with 
CAS and uPortal.
	For CAS, a new class is required that actually goes with the CAS 
client; it provides a JAAS LoginModule implementation that sits on top 
of the existing CAS java client.  It may be a while before this class 
shows up in an official CAS client release, but if anyone is interested 
in getting this enabled, let me know and I can email the source.  
Andrew Petro has volunteered to post the source on the CAS wiki as 
well.  I will send detailed instructions to the list on how to 
integrate with CAS to the first person who asks ;-)
	For uPortal, a simple web-proxyable channel has been added that gives 
a user a list of their authorized projects; this looks just like the 
initial screen of HC 1.4, but the links open HC2 in a separate window.  
This dashboard can be reached at any valid URL on the HC2 server by 
adding the parameter "mode=dashboard-portlet" (e.g. 
"https://hypercontent.columbia.edu/index.html?mode=dashboard-portlet"). 
  With CAS and the CASConnectionContext in uPortal, you can achieve 
single sign-on between the portal, the proxied dashboard channel, and 
the direct HC2 session, for a seamless user experience.

	I will be on vacation the first two weeks of August, and while I will 
make some effort to catch up with email every couple of days, I won't 
be doing any development work.  The only remaining "must-haves" for a 
final release are search-reindexing and lock-clearing scripts, which 
are of quite limited scope and should be complete shortly after I 
return.  I expect to have a final 2.0 release by the end of August, but 
I would stress that we are running the b4 code in production and have 
already migrated a number of sites, so the system has already endured 
some trial by fire.

Cheers,
	Alex