Ed Knutson wrote:
>
> > > 1. I think we can store the portlet markup as relational fields.
> > I think before we do this we have to ask ourselves where do we want the
> > Portlet Markup to permanently reside. In a file or in a db?
>
> It has to go in the database for persistence: I think we all agreed the
> filesystem would be a messy solution. With PortletMarkeup, we can specify a
> default set and a total set of portlets by writing a simple xml file. But when
> it gets stored, it is placed in a relational structure that conforms to the
> schema. It makes good sense to me then to reconstruct this xml from the
> database whenever it is requested, but then to cache this generated xml and use
> it if the user hasn't modified anything since the last request. That way, we
> don't have to totally rewrite the PortletFactory again: we can use the same
> system for both defaultPortlets.xml and individual custom user pages.
I agree. A decent solution is to have a XML Schema -> XSLT -> DB schema
creation. Then we can map out a peer system to to XQL/XPath queries.
> > I agree with you that there is a need for this type of documentation. I
> > also agree that the Jetspeed learning curve can be a deterrent to first
> > time contributors. Of course XML/XSLT are still very much moving targets,
> > maybe not so much the XML, but the transformations are definitely.
>
> A lot of Jetspeed has nothing to do with XML. By the time it gets to the API
> level, it's all pretty abstract. But, for somebody who doesn't know Turbine,
> Village, Castor, or ECS, what exactly is going on?
>
> First, a glossary of basic terms. Then a description of what processing
> actually takes place when Turbine starts up. Something like a roadmap of how
> the different branches of the API work together. It will be a nice complement
> to the descriptions of the components that the existing Turbine and Jetspeed
> documentation provide.
+1024. That is a good idea! I just put that note into CVS and
hopefully will include that in 1.2. May I suck at documentation :(
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
"For evil to win is for good men to do nothing."
--
--------------------------------------------------------------
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]
