| From | Sent On | Attachments |
|---|---|---|
| 242 earlier messages | ||
| Andre Kramer | Feb 26, 2003 7:08 am | |
| Richard Jacob | Feb 26, 2003 7:29 am | |
| Rich Thompson | Feb 26, 2003 7:30 am | |
| Rich Thompson | Feb 26, 2003 7:34 am | |
| Rich Thompson | Feb 26, 2003 9:37 am | |
| Rich Thompson | Feb 26, 2003 2:34 pm | |
| Rich Thompson | Feb 27, 2003 6:33 am | |
| Rich Thompson | Feb 27, 2003 6:40 am | |
| Rich Thompson | Feb 28, 2003 9:41 am | |
| Rich Thompson | Feb 28, 2003 9:54 am | |
| Rich Thompson | Feb 28, 2003 9:57 am | |
| Andre Kramer | Feb 28, 2003 9:59 am | |
| Rich Thompson | Feb 28, 2003 10:02 am | |
| Rich Thompson | Feb 28, 2003 10:11 am | |
| Rich Thompson | Feb 28, 2003 10:19 am | |
| Rich Thompson | Feb 28, 2003 1:05 pm | |
| Rich Thompson | Feb 28, 2003 1:11 pm | |
| Rich Thompson | Feb 28, 2003 1:15 pm | |
| Richard Jacob | Mar 3, 2003 6:57 am | |
| Rich Thompson | Mar 4, 2003 7:10 am | |
| Rich Thompson | Mar 4, 2003 7:12 am | |
| Rich Thompson | Mar 4, 2003 7:15 am | |
| Rich Thompson | Mar 4, 2003 7:32 am | |
| Rich Thompson | Mar 4, 2003 7:37 am | |
| Rich Thompson | Mar 4, 2003 7:40 am | |
| Rich Thompson | Mar 4, 2003 7:43 am | |
| Rich Thompson | Mar 4, 2003 7:45 am | |
| Rich Thompson | Mar 4, 2003 7:52 am | |
| Rich Thompson | Mar 4, 2003 7:55 am | |
| Rich Thompson | Mar 4, 2003 7:58 am | |
| Rich Thompson | Mar 4, 2003 8:05 am | |
| Rich Thompson | Mar 4, 2003 8:09 am | |
| Andre Kramer | Mar 4, 2003 8:29 am | |
| Rich Thompson | Mar 5, 2003 5:39 pm | |
| Rich Thompson | Mar 5, 2003 5:39 pm | |
| Rich Thompson | Mar 5, 2003 5:39 pm | |
| Rich Thompson | Mar 5, 2003 5:39 pm | |
| Rich Thompson | Mar 5, 2003 5:39 pm | |
| Rich Thompson | Mar 5, 2003 5:39 pm | |
| Rich Thompson | Mar 5, 2003 5:39 pm | |
| Rich Thompson | Mar 5, 2003 5:39 pm | |
| Rich Thompson | Mar 5, 2003 5:39 pm | |
| Rich Thompson | Mar 5, 2003 5:39 pm | |
| Rich Thompson | Mar 5, 2003 5:39 pm | |
| Rich Thompson | Mar 5, 2003 5:39 pm | |
| Rich Thompson | Mar 5, 2003 5:39 pm | |
| Rich Thompson | Mar 5, 2003 5:39 pm | |
| Andre Kramer | Mar 6, 2003 1:15 am | |
| Rich Thompson | Mar 6, 2003 3:28 am | |
| Andre Kramer | Mar 6, 2003 3:39 am | |
| Rich Thompson | Mar 6, 2003 3:43 am | |
| Rich Thompson | Mar 6, 2003 3:48 am | |
| Rich Thompson | Mar 6, 2003 4:01 am | |
| Rich Thompson | Mar 6, 2003 4:12 am | |
| Rich Thompson | Mar 6, 2003 4:19 am | |
| Rich Thompson | Mar 6, 2003 4:28 am | |
| Rich Thompson | Mar 6, 2003 4:38 am | |
| Rich Thompson | Mar 6, 2003 4:44 am | |
| Rich Thompson | Mar 6, 2003 4:51 am | |
| Rich Thompson | Mar 6, 2003 4:55 am | |
| Rich Thompson | Mar 6, 2003 5:23 am | |
| Kropp, Alan | Mar 6, 2003 10:33 am | |
| Rich Thompson | Mar 6, 2003 10:54 am | |
| Rich Thompson | Mar 7, 2003 4:32 am | |
| Rich Thompson | Mar 10, 2003 7:25 am | |
| Rich Thompson | Mar 12, 2003 7:46 am | |
| Rich Thompson | Mar 12, 2003 9:52 am | |
| Rich Thompson | Mar 13, 2003 6:17 am | |
| Subject: | RE: [wsrp-wsia] [change request #223] Supporting cloning requiressupporting releasePortlet | |
|---|---|---|
| From: | Andre Kramer (andr...@eu.citrix.com) | |
| Date: | Mar 6, 2003 3:39:54 am | |
| List: | org.oasis-open.lists.wsrp-wsia | |
Maybe we then need a boolean ServiceDescription.supportsExplictCloneAndSetGetProperties?
Or am I the only one that thinks properties are optional and separate from cloneBeforeWrite?
regards, Andre
-----Original Message----- From: Rich Thompson [mailto:ric...@us.ibm.com] Sent: 06 March 2003 11:35 To: wsrp...@lists.oasis-open.org Subject: RE: [wsrp-wsia] [change request #223] Supporting cloning requires supporting releasePortlet
I would prefer keeping releasePortlets() in the PortletManagement interface and let this conformance statement effectively state that those supporting cloning Portlets have to expose the PortletManagement interface. It would be odd to have the release operation separated from the clone operation.
Rich Thompson
Andre Kramer <andr...@eu.citrix.com> 03/06/2003 04:22 AM
To: wsrp...@lists.oasis-open.org cc: Subject: RE: [wsrp-wsia] [change request #223] Supporting cloning requires supporting releasePortlet
In that case, we should consider moving releasePortlet to the (required) markup factor? I would still like to have properties and clone optional for 1.0.
Should we also state whether a consumer releasing an offered portlet (one that has not been cloned) MUST be a null op or MUST throw a fault? I would prefer a null op as the consumer can always start using the portlet again.
regards, Andre
-----Original Message----- From: Rich Thompson [mailto:ric...@us.ibm.com] Sent: 05 March 2003 21:08 To: wsrp...@lists.oasis-open.org Subject: [wsrp-wsia] [change request #223] Supporting cloning requires supporting releasePortlet
Document: Spec Section: 8 Page/Line: 49/40 Requested by: Rich Thompson Old text: Any Producer that supports cloning portlets on performBlockingInteraction() or performInteraction() invocations SHOULD support the releasePortlet() operation.
New text: Any Producer that supports cloning portlets on performBlockingInteraction() or performInteraction() invocations MUST support the releasePortlet() operation.
Reasoning: Why wouldn't this be a MUST?
---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl> .... ....





