We have released the 2.6 alpha 2 release which contains the implementation of the important features of the 2.6 release.
The alpha 2 release also fixes the minor issues seen in the alpha 1 related to Oracle invalid table creation and WSRP deployment.
What's new since the 2.4 release ?
- Improvements of the dashboards with capability to edit private pages and copy a shared page to the dahsboard space
- More usability improvements : User / Role / CMS portlets redone
- WSRP 1.0 implementation
- flexible LDAP integration
- JMX invocation statistics of portlets
- CMS security improvements
- CMS Workflow
- Full implementation of JSR 168 portlet caching
Downloads from the download page http://labs.jboss.com/portal/jbossportal/download/index.html
The full alpha change log
Great work. I also downloaded the src for Alpha2. It needs to be tidied up. It's full of old java files that have been renamed. I couldn't do a full compilation from source.
I didn't have to do any patching to use Oracle 9i with CMs, so many thanks for that.
Also thanks to R.K. for fixing up JBoss Forums to work with the new portal code. At last we have a configuration that include facelets in a portlet.
Lastly, will a later release of Portal be implemented using Seam ? 3.x ?
Ok, in 2.4 sp1 pages are checked for security before being displayed as a tab in the navigation in
This seems to be handled by the psib request parameter (a map). In 2.4 the map only gives you PortalNodeURLs that you have permissions on, in all the 2.6 versions you get all the siblingURLs (your term in the JSP page).
Can this be fixed so that the psib parameter only gives you a handle to a map that gives you objects you have permissions to see?
I would like to inform that JBoss Forums 1.0.0 Beta has been released. Current version of Forums is compatible with newest Portal release. Go ahead and try it!
Congrats to Portal Team for bringing a really stable version already. I spent few nights with Alpha2 while migrating Forums and it worked smooth.
JBoss Forums Lead
JBoss Labs Team
Ok, another bug, this one is pretty major:
This happens when you reference js files in jboss-portal.xml to get the references in the html head on the page