[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: TransientProperties
Here is the writeup I volunteered to produce last week which extends
the current notion of PublicParameters to add transient property like
capabilities. This should get people's juices flowing: Summary: Address the various incoming requirements by adding two new concepts:
The second concept allows a producer to indicate whether the property it is placed in a global shared consumer space or a local per portlet space. The former allows two or more cooperating consumer component's to share a value while the later ensures the portlet has a discretely managed value [though this value may be impacted by others via a consumer supplied wiring mechanism]. Note: An open, unresolved issue is whether the transient property scope is considered part of the namespace or not. I.e. what do we do if two portlets publish a shared public parameter foo.bar but each publishes at a different transient scope [request and session]? Do we use these scopes as "hints" and defer to the greater scope [session]? Do we publish at each scope and view them as separate values? Setting values: A shared or local public parameter value can be set in a variety of ways:
Anyway: the structural details: For review: PropertyDescription [R] QName name [R] QName type [O] LocalizedString label [O] LocalizedString hint [O] string capabilities[] [O] Extension extensions[] TransientPropertyDescription extends PropertyDescription [R] string scope [wsrp:request, wsrp:session, .... open ended list so new scopes can be added] RuntimeContext [R] string userAuthentication [O] Key portletInstanceKey [O] string namespacePrefix [O] Templates templates [O] ID sessionID [O] Property sharedPublicParameters[] [O] Property localPublicParameters[] [O] Extension extensions[] -Mike- |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]