Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Sender: arkin@arkin.exoffice.com
Message-ID: <387B8911.BC1A7A6E@exoffice.com>
Date: Tue, 11 Jan 2000 11:48:33 -0800
From: Assaf Arkin <arkin@exoffice.com>
Organization: Exoffice
MIME-Version: 1.0
To: tomcat-dev@jakarta.apache.org
Subject: Re: You have to break eggs to make an omlette [was: LONG TERM PLAN]
References: <Pine.SOL.3.96.1000111102714.27286R-100000@tallest>
 <387B79E6.D4131E6@costin.dnt.ro>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Introspection would be nice thing to have, but rather limited in its
capabilities (I'm talking about Ant-like introspection).

However, having developed such an interceptor, if Tomcat can perform Ant
like configuration on the interceptor and map attributes into
properties, that would give my interceptor enough information to get up
and running, and won't bore me with DOM/XmlTree details.

Once I have that minimum set of information I can grab the proper
configuration file, which relies on substantially more complicated and
non trivial Java - XML mapping, or I can lookup them up in an LDAP
server, etc.

I believe that interceptors should either require simple configuration
which server.xml can contain, or complex configuration which should
exist outside of server.xml. This approach caters for the simple and
easy, as well as the overly complicated.

So, +1 on Ant-like introspection.

arkin


costin@costin.dnt.ro wrote:
> 
> "Anil K. Vijendran" wrote:
> 
> > On Tue, 11 Jan 2000 costin@costin.dnt.ro wrote:
> >
> > > Does everyone agree that tomcat.core will have a dependency on DOM ?
> > > ( tomcat.current doesn't - is this a feature we want for the new architecture?)
> >
> > Why? Is it because the interceptors are picked from server.xml and are
> > configured in by core?
> 
> One of the core interfaces in tomcat.next - Livecycle, has:
> configure( org.w3c.dom.Node ).
> 
> That mean components developed for tomcat.next require dom.
> 
> The current architecture is that each component has getter/setter for
> all properties of interest, and the configuration code calls them. That
> will also allow dynamic reconfiguration.
> 
> The "cleaned-up" architecture wants to use introspection, like in ant.
> 
> There are 3 models, and it seems everybody wants that we just throw
> away the last to and do the Tomcat.Next one.
> 
> Costin
> 
> >
> > It would be nice if core didn't have a dependency. It makes core lesser
> > embeddable. I'd like to see APIs that allow us to plug interceptors in and
> > the server.xml file is read and then these APIs are called at startup
> > time.
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org