Ok, I have Jetspeed more or less up and running, and am now in the
phase of finding out what it can really do, and how we can use it for
our portals.  If this information is of use to anybody, please add it
wherever it should go.

Jetspeed can show several different kinds of information.  For
example, the default page has the following areas, defined in
default.psml:

* Jetspeed: Its parent is JetspeedContent, which is a portlet for
  static news taken from a XML file called jetspeed-content.xml.

* Apache Jetspeed: Its parent is Jetspeed, whose parent is RSS, which
  is a portlet that shows RDF information.  The source for this is an
  XML file called Jetspeed.rss.

* Applications: Its parent is Applications, which is a portlet that
  encapsulates a whole application inside a portlet. This portlet will
  contain any portlets that have set the property application to
  "true".

* Search: Its parent is Search, whose parent is FileServer, which is a
  portlet that seemingly shows the contents of a static HTML file.  In
  this case, the file shown is static/search.html; this file even has
  Javascript code to show icons for different search engines.

* Slashdot: Its parent is Slashdot, whose parent is RSS.  So this
  should work just like Apache Jetspeed, but based on the contents of
  http://www.slashdot.org/slashdot.rdf.  It looks like it is expected
  that this URL will provide its contents in the RDF format.

* Apacheweek: Its parent is Apacheweek, whose parent is RSS.  This is
  identical to Slashdot, but the URL now is
  http://www.apacheweek.com/issues/apacheweek-headlines.xml.


The links that SHOULD be shown on my default screen, but are not:

* Mozilla: Its parent is Mozilla, whose parent is RSS.  This is
  identical to Slashdot, but the URL now is
  http://www.mozilla.org/news.rdf.  The log prints this error message:

    RSSPortlet:  Couldn't parse out XML document ->
    http://www.mozilla.org/news.rdf

  So it seems this site is not exporting its items in the proper
  format (or there is a bug in Jetspeed...).

* XMLHack: Its parent is XMLHack, whose parent is RSS.  This is
  identical to Slashdot, but the URL now is
  http://www.xmlhack.com/rss.php.  The log prints this error message:

    RSSPortlet:  Couldn't parse out XML document ->
    http://www.xmlhack.com/rss.php 

  So it seems this site is not exporting its items in the proper
  format (or there is a bug in Jetspeed...).


There are several other kinds of information that are not used on the
default page:

* PortletBrowser, parent Cocoon.
* PortletSearch, parent Cocoon.
* Customizer, parent Cocoon.
* XSPApplication, parent Cocoon.
* Cocoon: This portlet runs a generic XML file (program) through
  Cocoon.  Each portlet above sets its own file to be run.


* PortletInfoPortlet: This portlet shows information about other
  portlets.


There are eight other portlets that I know exist but don't know
anything about:

* GlobalAdminPortlet
* SelectPortlet
* JetspeedPropertiesPortlet
* MemoryStorePortlet
* JavaRuntimePortlet
* DaemonAdminPortlet
* JetspeedContentAdmin
* BadURLManagerPortlet


Open questions, that I hope someone will be able to answer:

* What is RDF?

* Why is there a JetspeedContent portlet and a RSS portlet?  I'm not
  sure the format for jetspeed-content.xml is RDF, but they seem to
  serve the same purpose... Or not?

* How does the layout work? What are the different ways of laying
  things out on a page? By column, by row, randomly (8-)?

* How should one change colors, look and feel, etc., for the whole
  portal?

* What are the little "edit" and "<square>" buttons on top of each
  area? Can one hook onto them to do something else? Can one add other
  buttons to the yellow title lines?

Thanks,


-- 
Gonzalo A. Diethelm
[EMAIL PROTECTED]


--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Archives and Other:  <http://java.apache.org/main/mail.html>
Problems?:           [EMAIL PROTECTED]

Reply via email to