Stefan Hepper
is the Software Architect for WebSphere® Portal, Workplace Client and
Server programming model, and public APIs. He co-led the Java™ Portlet Specification
Version 1.0 (JSR 168) and is now leading Version 2.0 (JSR 286). Stefan also started the Pluto
project at Apache that provided the reference implementation for JSR 168. Stefan has
delivered a number of lectures at international conferences, like JavaOne, and published
various papers. He is a co-author of
Pervasive Computing
and Portlets and Apache Portals.
Stefan received a Diploma of Computer Science from the University of Karlsruhe,
Germany, in 1995. After graduating, he worked for three years in the Research Center at
Karlsruhe in the area of medical robotics and component-based software architecture for
real-time systems. In 1998, he joined the IBM® Boeblingen Development Laboratory, where he
worked with Java Cards in the areas of security and card management. After working on
several pervasive computing standards, like Java Card Forum and SyncML, Stefan joined
the WebSphere Portal development team. He is currently the lead architect for the
WebSphere Portal and Workplace Client and Server programming model, and public APIs. In
this role, he works closely with customers to address their requirements and to make the
portal and workplace platforms extensible and well-structured. He co-led the
Java Portlet Specification JSR 168, and is now leading the follow-on version 2.0 as JSR 286.
Stefan also started the Pluto project at Apache that provides the reference implementation
for JSR 168. His research interests are component-based software architectures, pervasive infrastructures,
and, of course, portals and portlets.
Stefan lives in a small town in Holzgerlingen, near Stuttgart, Germany, which has a nice view
of the forest. Besides working and being with his family and friends, he likes skiing, motorcycling, and driving his old Porsche 914.
Since first versions of a standard or product typically focus on basic use cases with limited functionality, products supporting the specification end up adding on extensions to support more advanced scenarios. The second version of the Java Portlet Specification (JSR 286) is currently being developed to bring a standard solution and interoperability to accommodate most advanced use cases. Reviewing and providing feedback to the specification-in-progress gives you a way to make sure your specific needs are considered.
You can download this manuscript, which describes the different Apache Portals projects,
how portals work, how to write portlets, including portlets leveraging JSF, and how to create your own portal.
This is the first in a series of five articles that can help portal developers and
administrators to apply the IBM WebSphere Portal V5.1.0.1 programming model to your
company's portal. This article introduces the various parts of the model, provides a
short overview of portal technology, and describes how portals relate to the
service-oriented architecture (SOA).
This fifth article in the series on the programming model for IBM's SOA covers
services that are user facing, and services provided by users through the Human
Task Manager.
This articles compares the IBM portlet API and the new Standard Java Portlet API JSR 168.
It includes tips for migrating your IBM portlet to a JSR 168 portlet.
This paper describes best practices for designing and developing portlets that
conform to the JSR-168 standard, and which leverage the IBM WebSphere Portal infrastructure
for JSR 168.
This site covers specifications around Java. Even if these are sometimes hard to read,
it is often helpful to read the underlying specification of the technology you are using, understand what
really is specified, and what will work across different products.
