Two users look at the same portlet on their private page
Until they customize this portlet it is backed by only one instance on the Producer(efficiency)
What happens if they customize their portlet? (i.e. modify persistent state)
The Consumer cannot detect if customization is required (detecting edit mode is not enough)
The Consumer passes a flag to the Producer that indicates whether cloning is necessary and acceptable
If the portlet is shared AND the interaction induces a customization, then the Producer clones the portlet (if permitted) before performing the customization
Modes and Window States
Consumer managed (i.e. properties of the aggregated page)
Producer/Portlet request changes via:
1. Portlet URL parameters (wsrp-mode and wsrp-windowState)
=> Consumer MUST decide whether or not to honor the request BEFORE invoking the target operation
2. performBlockingInteraction() response
=> Consumer MUST decide whether or not to honor the request BEFORE invoking getMarkup() [any returned markup assumes the request is honored]
Markup Language Support
WSRP v1.0 defines fragment rules for:
WSRP v1.1 intends to additionally define fragment rules for:
WSRP v1.0 defines base set of CSS classes. This allows portlets to generate markup that automatically adjusts to the look and feel of the Consumer without having to know the vendor of the Consumer‘s implementation.
WSRP v1.1 intends to define additional CSS classes based on:
Submitted scenarios: It is recognized that the v1.0 classes do not cover all scenarios and additional scenarios are being sought.
Actual usage: As vendors submit the additional classes they define and the portlet controls those classes permit, the committee will consider adding such controls.
Leveraging Attachment Mechanisms
Attachment mechanisms potentially offer a substantial performance benefit as the attached documents do not have to be processed for insertion/extraction from the SOAP message.
Other standards bodies are working on standardizing attachment mechanisms, namely;
W3C XMLP Working Group
WS-I Basic Profile 1.1
WSRP v1.1 intends to track and leverage these mechanisms.
Leveraging Security Mechanisms
Due to the relative immaturity of message level security mechanisms, WSRP v1.0 depends only on transport security mechanisms.
Various OASIS Technical Committees (and others) are working on standarding message level security mechanisms, namely;