Re: [configuration] XmlConfiguration

[Martin Poeschl]

Henning P. Schmiedehausen wrote:

Martin Poeschl <[EMAIL PROTECTED]> writes:

Hi,

10 other projects also have their implementation and they don't want to switch :-((((

it definitly doesn't make sense to have 10 implemetations for something like reading an xml config file!!!
is it really impossible to find a solution which can be used by all projects??

let's join forces to find a way to have one configuration package!!!

Martin, the main problem might be that every application has a different
idea of how their XML markup should look like.

With properties it's easy:

foo.bar.baz = blo

with XML:

1) <property name="foo.bar.baz" value="blo"/>

2) <property name="foo.bar.baz">
   <value>blo</value>
  </property>

3) <package name ="foo">
    <package name="bar">
      <property name="baz">
        <value>blo</value>
      </property>
    </package>
  </package>

4) <property>
    <name>foo.bar.baz</name>
    <value>blo</value>
  </property>

And so on. Now find a common denominator. :-) The XMLConfiguration is
useless if we can't write a DTD for it.

right.

we should look which format is used by most of the projects in jakarta land.

maybe the target to replace existing code is unreachable :-(
but we can offer a working implementation and hopefully new projects will use our stuff and will not start another implementation.

martin

I personally would go for being able to parse 1 and 2. (3 is ugly and
4 is ambigous. What if there is more than one <name/> tag?. 1 is nice
and compact and 2 allows multi-value properties).

I got the code you sent me. Will look into it tonight.

Regards
Henning

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>