Dave Bryson wrote:
>
> "Kevin A. Burton" wrote:
>
> >
> > +1. It is funny that you jumped on this. I was about to as well :)
> >
> > The only requirement I have is that is uses XML as its repository
> > instead of SQL. Maybe I will write a way to have Turbine run from all
> > XML instead of hitting the database. Should just be a matter of meeting
> > the interface.
> >
> This is a trip! I ALMOST made it XML! I got this crazy idea after looking
> at Ant that maybe a SQL database was overkill for this. After all, it's just
> for persisting this stuff in the event of a system crash. Anyway, here's what
> I started but abandoned it for the SQL.
>
> Here's the XML file I had:
>
> <scheduledjobs>
> <jobentry name="TaskA" email="[EMAIL PROTECTED]" Task="YouJob">
> ` <runtime min="30" hours="-1" weekday="-1" daymonth="-1">
> </jobentry>
>
> *
> * //more jobs here
> </scheduledjobs>
>
> Anyway, this would be loaded (ant like) during start-up, Then when CRUDing jobs
> while
> the system was up you'd just simply flush to the XML file.
>
> What what the hell, should we change it to this?
<snip>
Why not do this for the time being? We could write an Interface like
the above XML (but in Java) then we could have support for XML and SQL
without having to do some major rework of persistence to solve this
problem.
Right now IMO XML isn't perfect for doign this:
- XMLSchema is not fully baked.
- There are no solid in-memory XQL/OQL/SQL databases
- XML with ASCII file persistence doesn't scale CPU/memory wise
- XMLSchema/XPath "id" suggestions are not used (no primary keys)
Why don't we use XML where it makes sense and just bridge out the
implementation. This way we can have the best of both worlds. This is
one of the approaches I plan on taking with Jetspeed.
Castor: (http://castor.exolab.org) I would like to push XML as the
persistence API as much as possible. The problem is the that developing
the SAX/DOM interface is very tedious/boring and a total waste of time.
Castor XML gets rid of this. You write an XML Schema and it will write
a whole package for you that can marshal and unmarshal the XML data for
you. It is APL the code is solid. I use it for about 3 XML APIs within
Jetspeed (Portlet Markup/Property Markup/RSS). It seriously reduced my
development time because I didn't have to write out code to parse my
XML.
Thoughts?
--
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."
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
