The following list details features found in this release of JBoss Portal. For a
technical view of the JBoss Portal features, refer to the
Project Roadmap and Task List
.
Technology and Architecture
- JEMS:
leverages the power of JBoss Enterprise Middleware
Services: JBoss Application Server, JBoss Cache, JGroups, and Hibernate.
- Database Agnostic:
works with any RDBMS supported by Hibernate.
- Java™ Authentication and Authorization Service (JAAS):
custom authentication via JAAS login modules.
- Caching:
utilizes render-view caching for improved performance.
- Clustering:
cluster support allows the portal state to be
clustered for all portal instances.
- Hot-deployment:
leverages JBoss dynamic auto-deployment
features.
- SAR Installer:
browser-based installer makes installation
and initial configuration a breeze.
Single Sign On
- Leverages Apache Tomcat and JBoss Single Sign On (SSO) solutions.
- Integrates with Java Open Single Sign-On (JOSSO) and Central Authentication Service (CAS) out of the box. Experimental support for the Open Web SSO project (OpenSSO).
LDAP
- Connect to virtually any LDAP server.
- Integrates with Sun™ Active Directory and OpenLDAP out of the box. Experimental support for Microsoft® Active Directory®.
Supported Standards
- Portlet Specification and API 1.0 (JSR-168).
- Content Repository for Java™ technology API (JSR-170).
- JavaServer™ Faces 1.2 (JSR-252).
- Java Management Extension (JMX™) 1.2.
- Web Services for Remote Portlets (WSRP) 1.0:
refer to WSRP
support in JBoss Portal for further details.
- Full J2EE™ 1.4 compliance when used with JBoss Application Server.
Portal and Portal Container
- Multiple Portal Instances:
the ability to have multiple portal
instances running inside one portal container.
- IPC:
the Inter-Portlet Communication API enables portlets to create links to other
objects, such as pages, portals, and windows.
- Dynamic:
the ability for administrators and users to create and destroy objects such as
portlets, pages, portals, themes, and layouts at runtime.
- Internationalization:
the ability to use internationalization
resource files for every portlet.
- Pluggable Services:
with authentication performed by the
servlet container and JAAS, it is possible to swap the authentication scheme.
- Page-based Architecture:
allows the grouping and division
of portlets on a per-page basis.
- Existing Framework Support:
portlets utilizing Apache Struts,
Spring Web MVC, Sun JSF-RI, AJAX, and Apache MyFaces are supported.
Themes and Layouts
- Swapping Themes and Layouts:
new themes and layouts
containing images can easily be deployed in WAR archives.
- Flexible API:
the Theme and Layout APIs are designed to
separate the business layer from the presentation layer.
- Per-page Layout Strategy:
different layouts can be
assigned to different pages.
User and Group Functionality
- User Registration and Validation:
configurable registration
parameters allow user email validation before activation.
- Workflow:
ability to define your own jBPM workflow on user registration.
- User Log In:
makes use of servlet container authentication.
- Create and Edit Users:
ability for administrators to
create and edit user profiles.
- Create and Edit Roles:
ability for administrators to create and edit
roles.
- Role Assignment:
ability for administrators to assign
users to roles.
- CAPTCHA Support:
distinguish between humans and machines when registering.
Permissions Management
- Extendable Permissions API:
allows custom portlet
permissions based on role definition.
- Administrative Interface:
allows permission
assignments to roles at any time for any deployed portlet, page, or portal instance.
Content Management System
- JCR-compliant:
the CMS is powered by Apache Jackrabbit, an open source implementation
of the Java™ content repository API.
- Database and File System Store Support:
configure the content store
for either a file system or an RDBMS.
- External Blob Support:
configurable content store, allowing
large blobs to reside on a file system, and content node references and properties to reside in an
RDBMS.
- Version and History Support:
all content edited and created is
auto-versioned with a history of edits, that can be viewed at any time.
- Content Serving Search-engine-friendly URLS:
http://your-domain/portal/content/index.html (does not apply to portlet actions).
- No Long Portal URLS:
serve binaries with simple URLs
(http://your-domain/files/products.pdf).
- Multiple HTML Portlet Instance Support:
allows extra
instances of static content from the CMS to be served under separate windows.
- Directory Support:
create, move, delete, copy, and upload
entire directory trees.
- File Functions:
create, move, delete, copy, and upload files.
- Embedded Directory-browser:
when creating, moving, deleting, or copying files, administrators can navigate the directory tree to find
the collection they want to perform the action on.
- Ease-of-use Architecture:
all actions to be performed on
files and folder are one mouse-click away.
- Full-featured HTML Editor:
the HTML editor contains a WYSIWYG
mode, preview functionality, and HTML source editting mode. HTML commands support tables,
fonts, zooming, image and URL linking, flash movie support, bullet and numbered list, and
dozens more.
- Editor Style Sheet Support:
to easily chose classes, the WYSIWYG editor displays the current portal style sheet.
- Internationalization Support:
content can be attributed to a specific locale, and then served
to the user based on his or hers Web browser settings.
- Workflow Support:
basic submit for review and approval process.