Hi again,
I seem to have forgotten to subscribe to the velocity-dev list
before mailing my DBResourceLoader proposal to it. Now I can't
easily reply to any of the replies to my original message. Duh!
Ok. Now that that's been taken care of (pat myself on the head):
All: The formatting of the inline code got messed up somehow.
Much of the formatting white-space got thrown away. It doesn't
look quite that "squished" in real-life... :-) I have found a
few code improvements already, btw. Oh, well. Seems that the
discussion soon got into the more intricate aspects of the
Velocity development which I won't interfere with. It is a
damn cool tool, that's for sure!
Geir: Sure, I could commit to at least support the code I took
part in writing and therefor know well enough to improve on.
Why I wrote it: The system I'm building is one where we are going
to run many (as in >100) sites simultaneously, with no filesystem
access for any of our users. The users can build, manage and
configure their sites using only a browser. All site structure,
pages, layouts and data are stored in a database. There are no
files making up a site structure, rather it is all described
via an XML document. All dynamic functionality is delivered via
a set of reusable components which we call modules. Think something
like a mix of Zope, HyperQbs and Jetspeed, conceptually. That's
why I needed the DBResourceLoader.
Other loaders: The ServletLoader sounds cool and could definitely
be an alternative solution for our system. Didn't think of that
approach before. Cool idea!
Take care!
--
David Kinnvall
Alert Investor Relations AB
+46 31 802640/10, +46 31 802670 (fax), +46 705 818432 (mobile)
