Dr. Dobb's Journal - September 2008 - (Page 59)

d09saund_p4ds 7/14/08 10:23 AM Page 59 by Shelly Saunders Core Technology .NET Development & the IBM WebSphere Portal Server Now .NET developers can have fun with portals, too Business users like web portals because portal views let them work with corporate data and business processes through a single, consistent UI. Software development teams like them because portals provide a comprehensive UI framework and the architectural opportunity to integrate applications in real-time at the front-end, rather than via potentially costly and unreliable offline batch processes at the back-end. Consequently, portals are increasingly considered an essential part of an enterprise SOA strategy. .NET developers, however, have had limited options when it comes to portals, since most high-end portals—BEA’s WebLogic Portal Server and IBM’s WebSphere Portal Server come to mind—are based on Java EE. In this article, I present techniques and examine tools for developing .NET applications for IBM’s WebSphere Portal Server. Shelly has worked in software development for 18 years and is a freelance software consultant. She can be contacted at shelly_saunders@bcs.org. JSR 168 The major portlet specification is JSR 168 (jcp.org/ en/jsr/detail?id=168), which ensures that portlets developed in Java can run on multiple portal servers. Many commercial and open-source organizations have adopted this standard, which defines the programming model for portlets and the contract between the portlets and the portlet container. The portlet lifecycle (Figure 1) consists of two main phases: • The processAction phase lets the portlet respond to events and has two parameters: ActionRequest and ActionResponse. ActionRequest provides access to information such as the request, the window’s state, the portlet session, and portlet preferences data. The ActionResponse object is used to change mode or state during the request. • The render phase is used by portlets to generate content as HTML fragments. It also has two parameters: RenderRequest and RenderResponse. The RenderRequest object provides access to similar information as the ActionRequest object. The RenderResponse object is used to return content, or delegate content to a JSP or servlet. The portlets are defined as a standard portlet descriptor file, portlet.xml; see Listing One. Within JSR 168 is consistent support for persistent and transient data management. Portlets can access two different types of persistent data: • Initialization Parameters. Read-only data defined in the portlet deployment descriptor file. Examples include the names of the files that make up the portlet. continued on page 62 September 2008 l www.ddj.com l Dr. Dobb’s Journal 59 http://jcp.org/en/jsr/detail?id=168 http://jcp.org/en/jsr/detail?id=168 http://www.ddj.com

Table of Contents Feed for the Digital Edition of Dr. Dobb's Journal - September 2008

Dr. Dobb's Journal - September 2008 Contents Friday Night Fish Fry Alia Vox Developer Diaries Developer’s Notebook A Conversation With Erik Demaine Application Lifecycle Management Meets Model-Driven Development Building a Robust Development Environment Real Users Really Matter Matching Wildcards: An Algorithm The Android Mobile Phone Platform Managing Application Thread Use Signalling Integer Overflows in Java .NET Development & the IBM WebSphere Portal Server The Agile Edge Effective Concurrency Swaine’s Flames

Dr. Dobb's Journal - September 2008

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.