[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 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] Conversely, we interpret a missing (empty) mode, to
mean maintain the current mode. 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]
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".
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]