OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-interop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [wsrp-interop] URL Templates: Should wsrp-mode and wsrp-windowState bepopulated when not changing



As part of looking for efficiency, the portlet developer is told to only encode changes in mode. This means the Consumer has to maintain a concept of the current mode as part of managing portlet state. One possibility is to encode this into the URL ... the difficulty in doing that (for that matter, encoding any type of portlet state) is templates now become mode/state-specific. Various strategies could be used to solve this, but I suspect they all involve the Consumer processing the URL either on the server or client tiers.

Rich



From: "Nader Oteifa" <nader2@netunitysoftware.com>
To: "'Nathan Lipke'" <nlipke@bea.com>, "'Ramaswamy, Satish'" <Satish.Ramaswamy@vignette.com>
Cc: Rich Thompson/Watson/IBM@IBMUS, <wsrp-interop@lists.oasis-open.org>
Date: 03/20/08 04:07 PM
Subject: RE: [wsrp-interop] URL Templates: Should wsrp-mode and wsrp-windowState be populated when not changing





But is it not difficult to maintain the current mode if templates are “true” templates and not re-write templates?  Where would you store the current mode if not part of the URL?
 
Nader
 



From: Nathan Lipke [mailto:nlipke@bea.com]
Sent:
Thursday, March 20, 2008 3:40 PM
To:
Ramaswamy, Satish
Cc:
Rich Thompson; wsrp-interop@lists.oasis-open.org
Subject:
Re: [wsrp-interop] URL Templates: Should wsrp-mode and wsrp-windowState be populated when not changing

 
Conversely, we interpret a missing (empty) mode, to mean maintain the current mode.

Nate

Ramaswamy, Satish wrote:

 
If the producer rewrites as wsrp-mode=&..., and the consumer accepts it,
how should the consumer interpret it?
 
Say the producer rewrites the links for the markup returned in the "Edit"
mode with wsrp-mode=, and the consumer does no further processing of
the returned markup,  when the user clicks on  this link, we are interpreting
wsrp-mode= as wsrp-mode not specified in the link and  defaulting to
wsrp:view
 
Satish
 
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent:
Thursday, March 20, 2008 2:04 PM
To:
wsrp-interop@lists.oasis-open.org
Subject:
Re: [wsrp-interop] URL Templates: Should wsrp-mode and wsrp-windowState be populated when not changing

 

My take is that a value should only be filled in if it is being changed. Due to the nature of templates, Consumers will need to accept wsrp-mode=& (i.e. the empty string as a mode value) to be the same as it not being specified (rather than it having a value of the empty string ...).


Rich


From: Nathan E Lipke <nlipke@bea.com>
To: wsrp-interop@lists.oasis-open.org
Date: 03/20/08 01:13 PM
Subject: [wsrp-interop] URL Templates: Should wsrp-mode and wsrp-windowState be populated when not changing

 







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.

 


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.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]