Here's another one: how about if we make JetspeedResources.properties into an
xml file? It would be easier to read and maintain, plus we could generate the
properties admin screen using a stylesheet. I think that would make web-based
editing more convenient.
Also, we seem to be reaching the point where there are some core packages and
optional packages. We could define a schema to mandate the core properties.
If optional properties aren't specified, the optional package won't be
initialized and that will keep the runtime memory usage down. Just have to
remember to add config buttons in the screen so the packages can be set up via
web later.
I should have an example JetspeedResources.xml in an hour or two.... I can
work on the parsing tomorrow.
Comments?
-ed
--
--------------------------------------------------------------
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]
