Re: [wsrp] Few clarifications on stateChange flag and consumer-managedstate

[Rich Thompson <richt2@us.ibm.com>]

The 2nd is not needed as the Producer
CAN NOT (stronger than MUST NOT!) return a registrationHandle from modifyRegistration.

The only setting of portletStateChange
that allows for cloning is 'cloneBeforeWrite' (section 6.4.3). The PortletContext.portletState
description explicitly connects the value supplied to the value in the
required portletHandle field. Personally this structurally states the equivalent
of the suggested conformance statement. However, if others think an additional
conformance statement does make sense, I would suggest adding it to 6.4.3
(where the semantics of the portletStateChange flag are discussed).

Rich

Subbu Allamaraju <subbu@bea.com>

03/16/06 09:38 AM

To	Rich Thompson/Watson/IBM@IBMUS
cc	OASIS WSRP TC <wsrp@lists.oasis-open.org>
Subject	Re: [wsrp] Few clarifications on stateChange flag and consumer-managed state

Rich,

I agree with that interpretation. But the spec does not specify that the
  producer MUST NOT return a new portletHandle when readRead is supplied
by the consumer.

In the case of registration, the producer MUST NOT return new 
registrationHandle in response to a modifyRegistration request.

I think both these are required since consumers may be using the handles
as keys in databases.

Subbu

Rich Thompson wrote:
> 
> PortletHandle is a required field in PortletContext and the semantics
> are that any portletState included in the PortletContext is relative
to 
> the portletHandle (Consumer MUST return it on future use of the 
> portletHandle).
> 
> I think this eliminates the need for the conformance statement as
it is 
> already encapsulated in the structure of the message.
> 
> Rich
> 
> 
> *Subbu Allamaraju <subbu@bea.com>*
> 
> 03/16/06 08:34 AM
> 
>                  
> To
>                  OASIS
WSRP TC <wsrp@lists.oasis-open.org>
> cc
>                  
> Subject
>                  [wsrp]
Few clarifications on stateChange flag and consumer-managed state
> 
> 
>                  
> 
> 
> 
> 
> 
> Mike Caffyn and I had some discussions on the correct interpretation
of
> the stateChange flag when the consumer is managing the state (via
> portletState).
> 
> Here are the possibilities:
> 
> Consumer: Sends a readOnly flag and portletContext
> Producer: Can either throw a fault if changes are required, or process
> normally but must not return a portletContext.
> 
> Consumer: Sends a cloneBeforeWrite flag and portletContext
> Producer: Returns a portletContext with a new portletHandle and possibly
> new portletState
> 
> Consumer: Sends a readWrite flag and portletContext
> Producer: Returns a portletContext with the *same* portletHandle and
> possibly *different* portletState.
> 
> I did a quick search in the Conformance spreadsheet and could not
find a
>  statement about whether "the producer MUST return the same
> portletHandle along with the same/modified portletState when consumer
> supplies readWrite".
> 
> If we have overlooked something, let me know.
> 
> I think the same question applies to modifyRegistration.
> 
> Regards,
> Subbu
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your
TCs in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
> 
> ---------------------------------------------------------------------
To 
> unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. You may a link to this group and all your TCs
in 
> OASIS at: 
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs
in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php