> Why not design the design the system in a modular way so that either a schema
> parser or an XML parser can be layered on an underlying engine. That way
> it doesn't get tied to a particular DB's schema syntax either. Then its
> up to us to write the parser we want if it's not there.
I like this option.
+1.
Have you seen http://www.melati.org - another servlet/webmacro/db framework in Java -
but I think its far less advanced - but the I like the looks of the db model - it uses
a DSD file to define the DB and produce a schema and Java classes/stubs from this. In
fact the system actually evolves the running db to match the DSD - cool - or dangerous
:-)
The DSD is not XML.
Chris
---
"surely it is madness to accept life as it is and not as it could be"
______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
