Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 95347 invoked from network); 29 Dec 1999 00:49:40 -0000 Received: from unknown (HELO arkin.exoffice.com) (root@207.33.160.104) by 63.211.145.10 with SMTP; 29 Dec 1999 00:49:40 -0000 Received: from exoffice.com (IDENT:arkin@arkin.exoffice.com [207.33.160.104]) by arkin.exoffice.com (8.9.3/8.9.3) with ESMTP id RAA01760 for ; Tue, 28 Dec 1999 17:02:56 -0800 Sender: arkin@arkin.exoffice.com Message-ID: <38695DC0.B77C4078@exoffice.com> Date: Tue, 28 Dec 1999 17:02:56 -0800 From: Assaf Arkin Organization: Exoffice X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13 i686) X-Accept-Language: en MIME-Version: 1.0 To: tomcat-dev@jakarta.apache.org Subject: Re: [LONG TERM PLAN] Proposed Architecture for Tomcat.Next Servlet Container References: <38691FD0.ACA719C@exoffice.com> <38693E55.B129B304@apache.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > Also, the Configurable pattern uses a Configuration object that is a > sort of configuration node of a configuration structure, something that > is much more useful than bean-like setter/getters even for the proposed > XML data binding which doesn't allow a great DTD complexity. We've been using XML -> JavaBean for configuration files and I'm quite happy with the results we've been getting. It's easier to work with than a more generic DOM or DOM-like model and moves the complexity from the application to the XML-Java marshalling framework. I'm not saying it's the only approach, but a darn good one and way less coding required. In the Tyrex configuration file I have some non trivial cases, e.g. I need to map an element to an object type specified in one of the object's attribute. The element maps to a generic DataSource interface, but the actual object created and configured is an implementation of this interface that can have any arbitrary set of properties that can't be expressed in a fixed DTD. Works like a charm. I also get to map the same object to two different element types, where the DTD (element name and attribute list differ) but the same implementation can be used in both cases. Also works like a charm. And in case we get too generic, a portion of the file can always be delegated as SAX events to some consumer, which we're using for the DSML portions that are handled by a direct DSML->LDAP mapping. arkin > -- > Stefano Mazzocchi One must still have chaos in oneself to be > able to give birth to a dancing star. > Friedrich Nietzsche > -------------------------------------------------------------------- > Come to the first official Apache Software Foundation Conference! > ------------------------- http://ApacheCon.Com --------------------- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org