Apache Jetspeed

Apache Jetspeed
Name	Apache Jetspeed
Developer	Apache Software Foundation
Released	2001
Programming language	Java
Platform	Java Servlet Container
License	Apache License 2.0

Apache Jetspeed Apache Jetspeed is an open-source portal framework that implements the Java Portlet Specification for building web portals and composite applications. It provides a server-side runtime and a suite of tools aimed at integrating portlets, content, and services from projects such as Apache Tomcat, GlassFish, JBoss, Liferay, and uPortal. Jetspeed has been used in enterprise, academic, and government contexts alongside technologies like Spring Framework, Hibernate, Apache Maven, and Apache Struts.

Overview

Jetspeed is a standards-based portal container implementing portlet APIs defined by the Java Community Process through the JSR 168 and JSR 286 specifications. It acts as a container for portlet components similar to how Apache Tomcat hosts servlet applications or how Eclipse hosts plug-ins. By integrating with web servers and application servers such as Apache HTTP Server, JBoss EAP, Oracle WebLogic Server, and IBM WebSphere Application Server, Jetspeed enables aggregation of content from disparate sources like Apache Sling, Apache Solr, and Microsoft SharePoint into unified portal pages.

Architecture

Jetspeed’s architecture centers on a portal container that manages portlet lifecycles, rendering, and user personalization. Core components include a Portlet Container following Portlet API semantics, a Page Composer integrating with AJAX libraries and Apache Wicket or JSF, and a security layer interoperating with LDAP, SAML, and OAuth 2.0 providers. Persisted configuration is often stored in relational databases such as MySQL, PostgreSQL, Oracle Database, or Microsoft SQL Server and accessed via JDBC and JPA implementations like EclipseLink or Hibernate. Jetspeed supports clustering through session replication strategies used by Hazelcast, Apache Ignite, and application server clustering features found in WildFly and GlassFish.

Features

Jetspeed provides features common to portal platforms: role-based access control integration with LDAP directories, personalization and user profile management compatible with OpenID Connect and SAML, and support for multi-tenancy suitable for deployments alongside Kubernetes and Docker. It supports drag-and-drop page composition similar to Liferay Portal and widget frameworks such as OpenSocial and WSRP. Search integration with Apache Solr or Elasticsearch enables indexed content discovery; content management connectors work with Alfresco, Drupal, and WordPress. Internationalization locales align with standards used by UNESCO publications and localization workflows found in Transifex and Crowdin.

Deployment and Configuration

Typical deployment involves packaging Jetspeed as a web application archive for servlet containers like Apache Tomcat or full Java EE servers like Red Hat JBoss EAP or Oracle WebLogic Server. Configuration is managed through XML descriptors and properties compatible with Apache Commons Configuration and build automation with Apache Maven or Gradle. Continuous integration pipelines often leverage Jenkins, GitLab CI/CD, or Travis CI with artifact repositories such as Nexus Repository Manager or Artifactory. For cloud-native deployment, administrators pair Jetspeed with container orchestration from Kubernetes and service mesh technologies like Istio to manage routing and observability provided by Prometheus and Grafana.

Security

Security in Jetspeed addresses authentication, authorization, and secure transport. Authentication commonly delegates to identity providers supporting SAML 2.0, OpenID Connect, or enterprise LDAP and Active Directory services. Authorization integrates with role mappings familiar to OAuth 2.0 resource servers and XACML policy engines. Transport layer security recommendations align with PCI DSS and NIST guidelines, using TLS configurations managed by Let’s Encrypt or enterprise certificate authorities like DigiCert. Auditing and compliance workflows are compatible with log aggregation stacks based on ELK Stack and monitoring frameworks such as Splunk.

Development and Extensibility

Developers extend Jetspeed by creating portlets using frameworks like Spring MVC, JavaServer Faces, Apache Struts, or Vaadin. Integration points include portlet filters, event channels per JSR 286, and servlet bridges for non-portlet webapps. Extension packaging uses OSGi modules in environments where Eclipse Equinox or Apache Felix are present, and dependency management aligns with Maven Central artifacts and Bintray-style registries. Contributors typically coordinate via Apache SVN historically and Git repositories hosted on platforms such as GitHub or GitLab, with issue tracking through JIRA or GitHub Issues.

History and Releases

Jetspeed originated as a project within the Apache Software Foundation in the early 2000s alongside other portal initiatives like uPortal and commercial offerings from IBM and Oracle. Major milestones include adoption of JSR 168 and later JSR 286 portlet standards, integration with OpenSocial specifications, and evolving compatibility with Java EE versions overseen by the Java Community Process. Over its lifecycle, Jetspeed has influenced portal patterns used in higher education deployments at institutions such as MIT, Stanford University, and University of California, Berkeley and in government projects referencing FedRAMP-style compliance. Its release history tracks incremental improvements in modularity, security, and standards alignment maintained by the Apache Software Foundation community.

Category:Java (programming language) portals