[EMAIL PROTECTED] wrote:
<snip>
> You mean something like a virtual db. I am tentatively +1 but am not sure
> it is a priority, at least for me. IMHO, This could take a fair amount of
> work to do right. I think it would be slick if we set up our own JDBC
> drivers for a virtual db. We could have linkings of virtual table -> db
> and tablename. It would be fairly straightforward for simple queries like
> 'select * from tablename;', but could get ugly with such things as joins
> because the joins could conceivably span 2 or more databases. Then there
> is the whole issue of parsing the sql
I am thinking of something like the Ozone XML persistence. It is pretty
slick but needs to be X database.
> I think for a first cut we go with a set up like Turbine where we have
> canned scripts to run against the database that creates and initializes
> the tables.
There is talk about doing that in XML Schema and just XSLT the schema
into database creation scripts.
<snip>
> 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.
:(
> I fought with whether or not to join Jetspeed with my calendar stuff
> because I didnt really know anything about the XM* technologies which are
> used heavily in Jetspeed. For me in the end, the added benefits of the
> portal functionality was key. On one hand, I could have a calendar that
> did x,y, and z or I could have a portal site w/ calendar.
>
> Certainly, anyone contributing to Jetspeed will have personal motivations
> and must be willing to learn. However, IMHO, anything we can do to reduce
> the learning curve for new developers will be beneficial to Jetspeed.
+1024.
> It would be cool if we could have a 'Learn to be a Jetspeed developer 7
> easy lessons :). I had found some links to some xml tutorials they could
> be a start.
That would be good. HREF links could be good for this type of stuff.
Also anyone that wants to improve the documentation and submit a diff
would be a god ! :)
Kevin
--
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]
