PortletStateChange handling in JSR case

["Richard Jacob" <richard.jacob@de.ibm.com>]

Hi all,

in our last call we discussed what vaues for PortletStateChange are
allowed/make sense in the JSR producer case and what returns a valid when
accessing POPs or CCPs.
Here is a short matrix to verify my understanding/kick off some discussion:

Consumer side:

1. accessing a POP
a. PortletStateChange=readOnly  -> ok allowed to do that
b. PortletStateChange=cloneBeforeWrite -> ok
c. PortletStateChange=readWrite -> doesn't make sense, is not allowed?,
expect fault from producer

2. accessing a CCP
a., b. and c. from 1. is allowed

Producer side:

3. POP being accessed
a. PortletStateChange=readOnly  -> should throw a stateChangeRequired fault
b. PortletStateChange=cloneBeforeWrite -> clone first, continue with action
on clone or throw a stateChangeRequired fault
c. PortletStateChange=readWrite -> makes no sense, throw OperationFailed

4. CCP being accessed
a. PortletStateChange=readOnly     -> throw stateChangeRequired fault
b. PortletStateChange=cloneBeforeWrite -> clone first, continue with action
on clone or throw a stateChangeRequired fault
c. PortletStateChange=readWrite -> ok, continue

Mit freundlichen Gruessen / best regards,

        Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development
Phone: ++49 7031 16-3469  -  Fax: ++49 7031 16-4888
Email: mailto:richard.jacob@de.ibm.com