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

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

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


Subject: [wsrp] What faults to throw when property writes are


Yesterday, we said we would continue to use this list for spec &
implementation discussion. So here goes one set of questions I would be
interested to hear people's opinion on:


In section 6.3.3 we say that "the producer MUST throw a fault message if the
processing the interaction requires changing its persistent state" if
"readOnly". We don't say what the fault MUST be. PortletStateChangeRequired
I presume ...

Later, we say that "Interface.PortletStateChangeRequired" MAY be throw if
the "producer implements access control that prevents Portlets from updating
persistent state". Surely that should be a security (Top Level Security.)
exception ;-)


Also, what actual fault should be thrown for the following cases (note that
not all the operations declare a throws PortletStateChangeRequired)?

- a Portlet attempts to set a property in getMarkup. 

Should the producer throw a fault or silently discard the update or generate
an error markup fragment?

- a Consumer attempts to update a preference on a publicly offered portlet.

Should the producer throw a fault or silently discard the update or generate
an error markup fragment? Can we allow  writes in some cases (admin level
consumers)?


While we are not required to align all the above, interop and testing would
be improved if we tighten property update fault semantics.

regards,
Andre


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