[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [wsrp-wsia] Portlet, Portlet Configuration, or Configured Por tlet
Yes. They will both be "Portlets", except that those created by clone-on-write or by clonePortlet (i.e. CCEs) will also be "Configured Portlets". Gil -----Original Message----- From: Subbu Allamaraju [mailto:subbu@bea.com] Sent: Monday, January 06, 2003 18:18 To: wsrp-wsia@lists.oasis-open.org Subject: Re: [wsrp-wsia] Portlet, Portlet Configuration, or Configured Por tlet Gil, I'm a bit confused by your suggestion at the end. Are you saying that the spec *will not* make any distinction between these two? If so, I second your suggestion. Regards, Subbu Gil Tayar wrote: > Thus, Portlet has no meaning in the spec (at least not in the > normative section, because the protocol ignores the issue of "type" > entirely), and we're left just with "Configured Portlet". > > As I said previously, I would make Portlet = POE and Configured > Portlet=CCE, and drop the old names. Two reasons: > > 1. CCE is badly named - the producer can, and in copy-on-write does, > create a CCE. 2. The POE is a portlet type. Even if two POEs have > _identical_ lists of properties, the Consumer _must_ treat them as > having different types. In other words, for POE's, the Consumer (and > the spec) cannot know that two POEs have the same type, and thus - > they have different type. > > So my suggestion again, is that POEs will now be called portlets, and > CCEs will now be called Configured Portlets, and both are "Portlets" > fronm the specs point of view. > > -----Original Message----- > From: Rich Thompson [mailto:richt2@us.ibm.com] > Sent: Thursday, January 02, 2003 20:44 > To: wsrp-wsia@lists.oasis-open.org > Subject: RE: [wsrp-wsia] Portlet, Portlet Configuration, or Configured Por > tlet > > > Having glanced at these, my suggestion would be: > > * Portlet: an object that implements a particular interface (e.g. > the Java Portlet interface) and which normally exposes a set of > configuration properties. For example, a "stock quote" Portlet may have a > "listOfStocks" property and a "numberOfStocksToDisplayOnFirstPage" > property. > * Configured Portlet: a Portlet with a particular configuration of > its properties. A Producer is a Web Service that publishes one or more > Configured Portlets; for example, two configurations of a "stock quote" > Portlet and a single configuration of a "weather" Portlet - the > specification calls these Producer Configured Portlets. The Consumer can > create additional configurations from these - which the specification > calls Consumer Configured Portlets. > > Rich Thompson > > > > > Gil Tayar <Gil.Tayar@webcollage.com> > 12/22/2002 02:43 AM > > To: wsrp-wsia@lists.oasis-open.org > cc: > Subject: RE: [wsrp-wsia] Portlet, Portlet Configuration, or > Configured Por tlet > > > An alternative to the three options below, is the following (quoted > from > the modified Primer attached): > * Portlet: a Producer implements Portlets. For example, a "stock > quote" Portlet and a "weather" Portlet. A WSRP Web Service can expose > multiple Portlets from one Web Service endpoint, which the Consumer can > use by sending the appropriate portletHandle. A Portlet is an object which > has a specific behavior - the data, business, and UI it exposes - and > specific configuration properties, which the Consumer and/or the End User > can set and thus configure the Portlet. For example, the "stock quote" > Portlet may have a "listOfStocks" property and a " > numberOfStocksToDisplayInFirstPage" property. > * Configured Portlet. Usually, the Consumer or End User do not set > the values of the Portlets pre-defined by the Web Service. Rather, they > create Portlets of their own, which are clones of the pre-defined > Portlets, and set the values of the properties of these new Portlets. > These Portlets, created by the Consumer or End User, are called Configured > Portlets, and they act just like any other pre-defined Portlet in that > their handle can be used anyplace a portletHandle needs to be sent. Note > that the specification does not assume that different pre-defined > portlets necessarily have different behavior. For example, it is perfectly > legal for the Producer to expose two "stock quote portlets", both having > the same behavior, and both having the same properties, but with different > values pre-assigned to those properties. This primer will not do this, and > there will be a one-to-one correspondence between the pre-defined Portlets > and their "type" (e.g. only one "stock quote portlet" and one "weather > portlet"). This primer will use the term Portlet to encompass both the > Pre-defined Portlets and the Configured Portlet, and use the specific > terms when there is a need to differentiate between the two terms. > > There is a significant difference between this suggestion and the > others - > this suggestion tries to differentiate between the Producer Offered > entities and Consumer Configured ones, and suggesting that there is > something "baser" about POE's than about CCEs. The reason why this > differentiation is important is because the spec defines this difference, > while our terminology only hints about it - the difference being that POEs > are returned by the service description (and thus are "base portlets" ) > and cannot be destroyed. > > So my suggestion is to use Portlets to encompass both Pre-defined > Portlets > and Configured Portlets (or Custom Portlets). > > Happy Holidays, > Gil > > -----Original Message----- > From: Gil Tayar [mailto:Gil.Tayar@webcollage.com] > Sent: Thu, December 19, 2002 20:30 > To: wsrp-wsia@lists.oasis-open.org > Subject: [wsrp-wsia] Portlet, Portlet Configuration, or Configured > Portlet > > As discussed in the teleconf - attached are three copies of the > Primer, > with the suggested names above inserted into the text, so that they can be > viewed in context. I believe we should close this issue ASAP, so enjoy > choosing between the three (and reading the primer :->)... > > Cheers > Gil Tayar > WebCollage > > > > ---------------------------------------------------------------- > 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>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC