"Kevin A. Burton" wrote:
> > That could just mean organizing the file we have (eg,
> > what is the difference between defaultportletcontrol.instance and
> > portletcontrol.defaultinstance?). Either way, I did complete a sample file, so
> > I'll add it to this mail, everyone can take a look, and we'll go from there....
> <snip>
>
> This is what I mean. There is no way that that is easier to manage than
> a .properties file.
>
> I am -1 for doing this. I went through this discussion in my head and
> it just doesn't make sense. Even the Cocoon project which within Apache
> has been more eager than any other project (less jetspeed) to except XML
> (IE that is why it is xml.apache.org) is still using their
> Properties/Configurations file.
>
I agree with Kevin that the Configuration stuff works for now, so let's keep it.
There's only one thing that's bothering me in the .properties file, it the
"XXXController" sections.
If we want to promote the creation of multiple controllers which would do smart
presentation stuff, the configuration items which are usually specific for a
controller should be in a separate (maybe XML) file. Because I don't think
modifying JetspeedResources to define a new property constant each time I want
to play with something is very practical (I don't even want to think about NOT
defining the constants...).
I think JetspeedResources.properties should be concern only the engine and the
Home
screen, modules configuration stuff belong elsewhere.
--
Rapha�l Luta - [EMAIL PROTECTED]
--
--------------------------------------------------------------
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]
