Michael Nash wrote:
>
> Mike, Kevin:
>
> Just my 2c worth, but the approach we've been taking with our portal project
> (which will integrate with Jetspeed) is very content-management oriented,
> but it's not contradictory with Jetspeed's approach: The actual content (or
> resources, as we call them) can be stored in any format, but the
> meta-content, the information about the content, is either XML or in a DBMS
> via JDBC. That way the content can be, as you say, very large, such as a
> CDROM's worth of info stored in PDF format - the portal simply delivers it
> (soon perhaps via portet mechanism :-) to the user(s).
>
> For smaller content, such as news, calendar, etc, the data of the content
> can be managed directly in XML.
>
> Again, this is just how we're doing it, not the only approach I'm sure.
I am +1 on having multiple content types other than XML. Portlets allow
this but right now we don't have an easy way for taking code in a DB and
pushing it with a Portlet. Maybe someone will hop on this but right now
it is not my highest priority.
Kevin
--
Kevin A Burton
http://relativity.yi.org
Message to SUN: "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]
