Re: [wsrp] [CR312] - Clarify InvalidSession fault description

While the proposed language does clarify
the intent of the fault, it does also make it sound like a requirement
is being placed on the Consumer to reinvoke the operation that caused the
fault. We have in general left such decisions to Consumer policy and so
I would propose the following refinement:

New Text: 

InvalidSession: Used only when a Producer
session has expired and in
order to process the request, the Producer
will need
the Consumer to reinvoke the operation resending the user profile and
URL templates which may have been stored in the Producer session. If both
userContextStoredInSession and templatesStoredInSession fields of the PortletDescription
type are false, Producers are encouraged to reinitialize the session in
stead of returning the InvalidSession fault. Producers
should note that whether or not the Consumer actually reinvokes the operation
will be a matter of Consumer policy.

Rich 

Rich Thompson/Watson/IBM@IBMUS

02/07/05 02:19 PM

To



cc

Subject

[wsrp] [CR312] - Clarify
InvalidSession fault description

Document: Specification 

Requested by: Subbu Allamaraju 

Section: Section 13 

Page: 76 

Old Text: 

InvalidSession: Used only when a Producer session has timed out AND the

Producer needs the Consumer to invoke resend data that may have been 

cached in the session. 

New Text: 

InvalidSession: Used only when a Producer session has expired and
the 

Producer needs the Consumer to reinvoke the operation resending user

profile and URL templates that may have been stored in the Producer 

session. If both userContextStoredInSession and templatesStoredInSession

fields of the PortletDescription type are false, Producers are 

encouraged to reinitialize the session in stead of returning the 

InvalidSession fault. 

Compatibility Issues: None 

Reasoning: The original statement is not clear. The new text clarifies

the issue, and includes guidance.