Re: [Documentation] Builder-docs

[Gerard van Enk]

Kees Jongenburger wrote:

I've added 2 things to the builder.dtd, a parameter name to the
buildertag and a descriptions/description tag to the field tag. The
first one is needed because there was no buildername inside the
builder.dtd and xslt can't read the filename (which is the buildername).

Hi

I think the changes are just great. Adding a name is one thing we realy should have done earlier. But I considder this a big change that should be tested at least with the folowing stuff

-reading configuration (making shure name and the file name are equals otherwize print a big error). if the file name and the name attribute are not the same we can't find builders any more.

Maybe we have to switch (after 1.6 has been released) to using only the name inside the builder.xml?

-exporting applications

-editing nodemanagers using the jsp /scan admin pages

-The xml reading classes now have methods that have 2 arguments the builder name and the configuration. That should also be changed.

I don't get this, but maybe it's too early this morning :)

I just think we can't make such a change 3 day's before the code freeze
Or have you been testing this already?

I'm working on the export things....

An other thing is the work I have been doing the last weeks. I have been creating a set of java interfaces to that define a nodemanager configuration
those classes can read and write builder xml configurations. If we are making big changes to the configuration stuff I would like to make a proposal to use the java interfaces as mean to communicate with the cloud. This would finaly make in possible to change the xml location/format without having to change every class using the configurations directely.

I think one of the goals for 1.7 had to be to create an administration api for everything that can be adminstrated :)

Gerard