WSRP Interfaces Consumer Defined Portlet Hierarchies Goals Introduction

WSRP Interfaces Consumer Defined Portlet Hierarchies

Goals Introduction of Feature to TC n Gather Feedback To Use Within Subcommittee Discussion n

Feature Status Initial Feature Proposal Draft n Some Subcommittee Email Discussion n

Problem Statement n WSRP 1. 0 doesn’t provide a mechanism to allow reconfigurable portlet state to be shared amongst users. n Simple Use Case – Configuring SMTP Server for an Email Portlet

General Approach n Introduce CCP Hierarchies Parent CCP {Handle, State} Child CCP {Handle, State}

Open Question –What State Can Be Shared? n Portlet Properties Useful to simplify portlet development n Simple Example – Property to Specify SMTP Server n n Opaque Portlet State Useful when complex UI is necessary n Simple Example – Selecting a Content Folder within the Directory Tree of a Content Repository n

Open Question – What are The Hierarchy Semantics? Inheritance Occurs From Parent to Child Only n Declaring Properties “Final” n Properties Set on a Child are “Protected” n Unlimited Hierarchy Depth n

Open Question – Is a Config Portlet Mode Useful? Allows Portlet Developer to Explicitly Prohibit User Customization of State n Allows Portlet Developer to Empower Consumer Administrators to Prohibit User Customization of State n

Next Steps Answer Open Questions n Finalize Use Cases and Feature Proposal n Begin Feature Specification n