Say the portlet (A) in the page designer use
case to be cloned/copied has properties and values: x=1 and y=2. The new copy/clone
(B) would initially have the same property values for simple non-computed
properties, but what about after:
A.x = 3;
B.y = 4;
What is the expected resultant value of
A.y? So far, we have made no assumptions here (the write to A.x could also
modify A.y if y was computed from x), but I would expect a copy/clone across registrations
to help preserve A.y == 2. If we named the operation "copy" then I
would be further encouraged to expect no post copy relationship between A and B,
even if the two registration handles happen to reference the same registration,
and this would, I think, be expected by Rich's use case, but not our
necessarily our 1.0 clonePorlet.
Do we agree that there are such use cases
where breaking any relationships between a portlet and its copies/clones is a requirement?
If so, then a new copyPortlet operation makes sense (rather than overloading
clonePortlet). Computed properties can still take on any value they like, but
we would be encouraging producer/portlet property relationships to respect
registrations.
Regards,
Andre
From: Goldstein, Scott
[mailto:]
Sent: 04 October 2004 18:04
To: Andre Kramer; Rich Thompson;
Subject: RE: [wsrp-interfaces]
copyPortlet - additional use case
If I understand correctly, the only
difference between clone and copy is the relevance of the registration.
Therefore, I would say that this use case is applicable for both clone
and copy. The clone() method, I believe, currently supports this use case
due to the requirement of copying the current state from the original portlet
to the clone being created. Is this not true for copy() as well?
Scott
From: Andre
Kramer [mailto:]
Sent: Monday, October 04, 2004
8:34 AM
To: 'Rich Thompson';
Subject: RE: [wsrp-interfaces]
copyPortlet - additional use case
Could be
applicable, I agree. In selecting the use case, focused on requiring two
registrations and involving an end user.
Regards,
Andre
From: Rich
Thompson [mailto:]
Sent: 04 October 2004 14:33
To:
Subject: [wsrp-interfaces]
copyPortlet - additional use case
I wonder if the following is not another use case that the copyPortlet factory
proposal is seeking to solve (note that the problem this use case raises is
more acute when portlet hierarchies are involved):
A page
designer spends a significant amount of time tweaking the customizations of a
portlet for a particular set of pages in order to provide maximum benefit to
the users of those pages. The page designer is then given a task for another
set of pages for which use of that same portlet will only require small changes
in the set of customizations used for the first set of pages. Rather than
starting again or (potentially) having future changes to the customizations of
the first portlet bleed into the pages using it the second time, the page
designer would like to produce an independent copy of the customized portlet
and use that as the starting point for the work on the new set of pages.
Rich
09/27/2004
11:45 AM
To
cc
Subject
[wsrp-interfaces] Groups - wsrp-2.0-3-props-ak-270904.zip
uploaded
The
document wsrp-2.0-3-props-ak-270904.zip has been submitted by Andre Kramer
() to the WSRP Interfaces SC document repository.
Document Description:
Updated from (22/09) conf call discussions and
inputs to getResource
Download Document:
http://www.oasis-open.org/apps/org/workgroup/wsrp-interfaces/download.php/9429/wsrp-2.0-3-props-ak-270904.zip
View Document Details:
http://www.oasis-open.org/apps/org/workgroup/wsrp-interfaces/document.php?document_id=9429
PLEASE NOTE: If the above links do not work
for you, your email application
may be breaking the link into two pieces.
You may be able to copy and paste
the entire link address into the address field of
your web browser.
