Ed Knutson wrote:
>
> > -1 for storing XML in the DB right now. Not unless we can map the XML
> > schema out into a DB schema.
>
> IMPORTANT ISSUES:
> 1. I think we can store the portlet markup as relational fields. Would it be
> better to write a new PortletFactory.getInstance() that receives a
> TurbineUserPeer as a parameter, or write a Cocoon (something-or-other) that
> retrieves this info from the db and formats it with a stylesheet to PSML, whose
> url may be supplied to the existing PortletFactory via RunData?
... I would rather this not be JS specific. It would be essentially
defining a different storage format for XML.
> 2. Turbine comes with stored sql procedures for setting up the database. I
> think we should have a separate Jetspeed database. In fact, I think we should
> be able to specify a different database for each table, with the option to
> share. This will make clustering easier in high-performance environments.
... No thoughts here. Just that this is a development nightmare. Some
of this is just thinking out in the open but if we had an XML engine,
maybe similar to the one in Ozone but portable across all databases we
could get rid of this issue. Maybe through a mapping layer as in JDO.
> 3. Should the administrator be forced to set up each table, or should Jetspeed
> have some amount of control over this (such as creating a certain table if it
> doesn't already exist)?
Most good DBAs like to run under a database user who only has SELECT,
INSERT, DELETE and UPDATE rights. This wouldn't work in that env.
<snip>
--
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]
