URL Templates: Should wsrp-mode and wsrp-windowState be populatedwhen not changing

[Nathan E Lipke <nlipke@bea.com>]

We planned on discussing this on the call today, but I guess its canceled.

Satish and I have been emailing back and forth over an incomparability between the Vignette  consumer and the BEA-WLP Producer.

The Vignette consumer switches the portlet to edit mode (via a title bar button) and calls getMarkup with the performBlockingInteraction template including {wsrp-mode} and {wsrp-windowState}. The BEA-WLP producer returns markup containing a form with an action URL using the performBlockingInteraction template. The {wsrp-mode} and {wsrp-windowState} are replaced with the empty string. This results in the producer incorrectly sending a mode of wsrp:view in the performBlockingInteraction request.

The question is, should the producer fill in the current mode and windowState in the templates when the producer does not wish to change them?

Here's the spec wording:

9.2.1.5 wsrp-mode

Activating this URL includes a request to change the mode parameter in MarkupParams into the mode specified as the value for this portlet URL parameter. The value for wsrp-mode MUST be one of the modes detailed in [Section 5.9] or a custom mode the Consumer specified as supported during registration. The wsrp-mode portlet URL parameter MAY be used whenever the wsrp-urlType portlet URL parameter has a value of "blockingAction" or "render".

9.2.1.6 wsrp-windowState

Activating this URL includes a request to change the windowState parameter in MarkupParams into the window state specified as the value for this portlet URL parameter. The value for wsrp-windowState MUST be one of the values detailed in [Section 5.10] or a custom window state the Consumer specified as supported during registration. The wsrp-windowState portlet URL parameter MAY be used whenever the wsrp-urlType portlet URL parameter has a value of "blockingAction" or "render".

Thanks,

Nate

Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.