Ed Knutson wrote:
>
> 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.
+0... no real opinion here. Our properties subsystem works fine and I
don't really see why we should be using XML if something conventional
works just fine. However, I think that there are some advantages that
XML gives us like with Portlet Markup or Stylebook. If we are going to
redo our Configurations infrastructure it would be X-project (Cocoon,
Turbine, Jetspeed) and not just Jetspeed. The other drawback is that
every project would need to include Castor.
> 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 don't really see the advantage here. It would have to be smart enough
to know what these missing properties are. That and if they aren't used
they will get garbage collected.
> I should have an example JetspeedResources.xml in an hour or two.... I can
> work on the parsing tomorrow.
<snip>
Don't bother with the parsing. Use Castor :) That is what it is there
for. I have already defined a Properties XML Schema that might be
useful. I experimented with marking up properties in feeds.xml.
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]
