portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Weaver, Scott" <Swea...@rippe.com>
Subject RE: My idea and implementation about 'portlet category'
Date Tue, 08 Oct 2002 12:59:47 GMT
You could specify default categories for individual portlet types (RSS, OCS, etc.).  Then,
when a portlet is dynamically created, automatically assign the pre-determined category for
that portlet type to the new portlet.

Example: all dynamically created OCS feeds get the initial category of "OCS Feed".  

A more advanced and possibly more effective way would be through a simple event model.  You
could register listeners for each specific portlet type.  When a portlet is created, a message
is sent to all listeners that includes the type of portlet created and the event type, at
this point only "Created".  The correct event listener would then proceed to due whatever
it needs to, in this case, it would create category entrty(ies) for the new portlet entry.
 The benefit of using the event model is that it would allow us to be more specific in terms
of categorizing an entry than just tying in a default category.  Then event listener could
inspect the contents (data, headlines, titles, etc) of the new portlet and create category
entries based on those contents.

Just some ideas,

> -----Original Message-----
> From: Luta, Raphael (VUN) [mailto:Raphael.Luta@groupvu.Com]
> Sent: Tuesday, October 08, 2002 3:53 AM
> To: 'Jetspeed Developers List'
> Subject: RE: My idea and implementation about 'portlet category'
> I personnally like the idea of decoupling the taxonomy from the portlet
> definitions
> but how do you plan to categorize dynamically created portlets (like the
> ones created
> by the OCS feed ?)
> > -----Message d'origine-----
> > De?: Ocean Dong [mailto:odong@sh.symbidia.com]
> > Envoyé?: mardi 8 octobre 2002 06:05
> > à?: jetspeed-dev@jakarta.apache.org
> > Objet?: My idea and implementation about 'portlet category'
> >
> >
> > Jetspeed1.4 has introduced 'category' idea for portlet, but i
> > feel current design, implementation and use of portlet
> > category seems a little ambiguous. My company is working on
> > jetspeed, and i redesign and implement portlet category
> > function. There are two main desicion i have made:
> >
> > 1, portlet's category info should be separeted from portlet's
> > self definition(in the xreg file)
> > 2, admin is (and common user may also be) able to customize
> > the whole category info hierarchy by logging into jetspeed.
> >
> > As a result, i has designed a simple xml schema to store
> > category info, provided a turbine service for read/write
> > category info, wrote a special portlet to manage category
> > info, and changed the jetspeed customizer a little for adding
> > the support of category when selecting portlets.
> >
> > The design and implementation is simple and unmature, but i
> > think the basic idea is helpful. if anyone (especially
> > contributors of jetspeed) is interested in what i have done,
> > please refer to http://rd.sh.symbidia.com/~ocean/en/work.htm.
> > I hope that can be contributed to jetspeed source.
> >
> > thanx a lot!
> >
> >
> --
> To unsubscribe, e-mail:   <mailto:jetspeed-dev-
> unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:jetspeed-dev-
> help@jakarta.apache.org>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message