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

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-interfaces message

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


Subject: Re: [wsrp-interfaces] Groups - Import_Export.html uploaded


Thanks for the response.  My replies:
  1. Point noted on the confusion of passing PortletContexts to getPortletStates().  I had a similar concern hence the Question raised about it.  We can poll the larger group on Wednesday.
  2. ClonePortlets() is meant to pertin to both CCPs and POPs just a a regular clonePortlet().
  3. Yes, I am suggesting a minor change in interpreting the spec.  I suggest that the supplied PortletState overrides/becomes the PortletState of the clone.  To a certain extent this occurs in the case of consumer managed PortletState as the producer would never know.  The subtle change is that it would also impact producer managed PortletState.
  -Mike-

Coco, Christopher wrote:
Just a couple of points.

I agree with the point you made that if you're expecting Producers to maintain some type of versioning
for PortletState that this responsibility should be mentioned in the spec or at least in the primer.

I think it seems a bit circular to pass an array of PortletContexts to the getPortletStates() method, 
in that you are trying to get PortletStates yet you are passing in objects that contain PortletStates. 
I think it adds a level of confusion that can be easily avoided. You then don't have to  add the caveat 
that the PortletState of each PortletContext needs to be nil and if its not the Producer must ignore it, 
etc, etc. I would say that it makes more sense logically to only require an array of PortletHandles. 

It is not clear if the clonePortlets() method is meant to pertain to CCPs or POPs (or is it both?). If
we're trying to additionally create a way to do bulk cloning (outside of the reasons for import/export)
then I can see that this method can be used for both CCPs and POPs and I agree that it would seem safer 
to include the old handle along with the new handle -- but you could also argue that same should be true 
for a simple clonePortlet() call. I don't particularly like relying on array indicies to indicate the 
relationship between the request list and the response list, but it would seem that without adding 
another field to the PortletContext (something like, originateHandle -- which when nil means the 
PortletContext refers to a POP), then we might just have to live with the one to one correspondence.

In the handling imports section, are you saying that it will be expected of the Producer that when
a clonePortlet() call is made and the handle refers to a POP and state is supplied, that the initial
state of the clone will be the supplied state instead of (as I interpretted) as the spec says, 
"the initial state of the new Portlet MUST be equivalent to the state of the Portlet referenced by
the supplied handle." which would be the state of the POP referenced, not the supplied state in the
PortletContext? Currently, I think that most Producers would ignore a non-nil PortletState when the
handle references a POP, but it seems like you might be saying that should no longer be true, correct?

Thanks,
Christopher

Christopher Coco
Senior Software Engineer
Vignette Builder
p. 415.995.3534 | f. 415.975.9801

Vignette's software and expertise help organizations harness 
the power of information and the Web to deliver measurable 
improvements in business efficiency. Vignette is the efficiency 
expert. Visit http://www.vignette.com/ to learn more. 



-----Original Message-----
From: Michael.Freedman@oracle.com [mailto:Michael.Freedman@oracle.com]
Sent: Thursday, July 01, 2004 9:26 AM
To: wsrp-interfaces@lists.oasis-open.org
Subject: [wsrp-interfaces] Groups - Import_Export.html uploaded


The document Import_Export.html has been submitted by Michael Freedman (Michael.Freedman@oracle.com) to the WSRP Interfaces SC document repository.

Document Description:


Download Document:  
http://www.oasis-open.org/apps/org/workgroup/wsrp-interfaces/download.php/7534/Import_Export.html

View Document Details:
http://www.oasis-open.org/apps/org/workgroup/wsrp-interfaces/document.php?document_id=7534


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.


  



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