Paul Spencer wrote:

> I have been working with Jetspeed v1.3a1 and the current CVS.  I am
> excited by the new features that I have see in the CVS! Great work!
> 
> I am building a portal to present production data.  The user of the
> portal range from management to engineers and lab technicians.  Content
> for the portlets is generated from a database.  The types of content
> displayed in include graphs (JPEG/BMP/SVG), Lists (via RSS) and mini Web
> pages (HTML).  I currently display the desired content using the CVS and
> configuring portlets.xreg.
> 


Just a quick tip: don't use portlets.xreg but rather a local portlet registry
like local-portlets.xreg. This way if/when you upgrade your jetspeed version,
you'll only need to copy your local file to the new webapp and not try to merge
any difference that may occur between the default Jetspeed portlets.xreg and
your own version.


> Requirements/Environment:
> o Initially their will be 100+ portlets.
> 
> o New portlets will be created all of the time.  The portlet
> configuration can easily be extracted from a database.
> 
> o The list of portlets available to a user will be limited based on
> Jetspeed users and roles.
> 
> o Portlets will be organized into logical groups, i.e. "Production Area
> 1 Management".  The portlets should be presented to the user in logical
> groups, see the example below.
>     Production Area 1 Management
>         Daily Report
>         Production Summary by Shift
> 
>     Production Area 2 Management
>         Daily Report
>         Production Summary by Shift
>    
>     Mill Summaries
>         Daily Report
>         Production Summary by Shift
> 
> Questions:
> 1) Can portlets be added while jetspeed is running?
> 


Yes. Simply add their definition in the xreg file and drop the classes in
/WEB-INF/classes


> 2) Can jetspeed get the portlet configuration from a database?
> 


Not as default, but it's just a matter of implementing a Registry service
backed by a DBMS instead of XML files. Using Castor JDO for thisq purpose
should be very easy.


> 3) Can the list of available portlets be presented in the Customizer as
> described above?
> 


Since your definitions are local, you'll probably have to modify a little
the browser code/template but this does not present major issues. You can
only play with this by customizing the default portlet-registry-browser
portlet. I've not yet linked the protlet browser with the customizer.

--
Raphael Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Paris


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to