tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Todd <>
Subject Re: [Catalina] Discussion - Component Configuration Strategy
Date Mon, 24 Jan 2000 04:55:07 GMT

John Holman wrote:

> > One aspect of the proposed architecture is certain to engender further
> > discussion -- the use of the org.w3c.dom "Node" interface as the means
> > by which components receive their component configuration information.
> As well as the general strategy for configuration there is still this issue
> of the API for accessing  the configuration data itself. Rather than using
> the DOM directly (as e.g. in Craig's original proposal) I'd suggest a
> simpler interface that is oriented more towards representing configuration
> data (as opposed to documents) and which should be as well suited to an
> implementation based on say LDAP or properties files as it is to XML.  These
> advantages of abstraction and simplification should outweigh any
> disadvantage of introducing an additional layer - especially since
> performance is not really an issue in this context.
> For example I've used the following interface to represent configuration
> data
> public interface PropertyTree {
>     String getName();
>     String getValue();
>     java.util.Enumeration getAttributeNames();
>     String getAttribute(String name);
>     java.util.Enumeration getChildren();
>     java.util.Enumeration getChildren(String filter);
>     PropertyTree getFirstChild();
>     PropertyTree getFirstChild(String filter);
> }

this is pretty much how XMLTree, possibly badly named as it is,
is designed with the exception of the getFirst() methods. just trying
to point out some alignment potentials here with the hopes of raising
the bar on design/architecture discussions.

hope this helps,

- james

View raw message