Re: [wsrp-conformance] cloning and setPortletProperties

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

I would expect the same fault to be
thrown as if an opaque action tried to update persistent state on a portlet
without allowing for implicit cloning. It is a good errata item.

Rich

Subbu Allamaraju <subbu@bea.com>

07/08/2004 10:14 AM

To	wsrp-conformance@lists.oasis-open.org
cc
Subject	[wsrp-conformance] cloning and setPortletProperties

I've a question on invoking setPortletProperties on
a POP.

I searched the spec, but could not find any reference to this question.
I did find an assertion statemenet (AS109) which reads

"The properties of a cloned portlet may be set explicitly (via 
setProperties()) or opaquely (via "wsrp:edit" mode)."

[I just noted that the operation name needs to be corrected in this 
statement.]

So, my question is whether it is valid to invoke setPortletProperties on
a POP? The spec says that POPs are not modifiable, but we don't 
explicitly define what cannot be modified.

Thanks

Subbu

To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsrp-conformance/members/leave_workgroup.php.