Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Message-ID: <37964B30.77D7C82F@eng.sun.com>
Date: Wed, 21 Jul 1999 15:35:28 -0700
From: James Todd <james.todd@eng.sun.com>
Organization: Sun Microsystems
MIME-Version: 1.0
To: tomcat-dev@jakarta.apache.org
Subject: Re: request for review: server/config discussion
References: <DC37797EB8C3D21197280008C74C893DF119BE@USAMCMS2>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Carreira, Jason" wrote:
> 
> > -----Original Message-----
> > From: James Todd [mailto:james.todd@eng.sun.com]
> > till then, i've just kick started this discussion with
> > a supporting "request for discussion" doc to capture the
> > goals and decission points. i'm bringing to the table a
> > practical perspective to a portion of code sun will be
> > contributing (jswdk: servlet and jsp ri coupled with an
> > http 1.0 server all implemented in 100% java which has
> > an xml configuration element and is gaining more, namely
> > j2ee deployment descriptors) and some ideas as to where
> > this theme could/should proceed.
> 
> Would those be the XML deployment descriptors from the EJB 1.1 spec? People
> on the EJB-INTEREST mailing list were not too thrilled with those, because
> the data couldn't be validated by a validating parser (not sure of why, I
> haven't finished my XML homework!) so maybe that would be a problem here,
> too?
> 

not directly. with tomcat there are two areas of configuration,
each of which is formatted in xml yet one is, at the moment,
specified by tomcat whereas the other is indeed specified by
j2ee (ejb, servlet, etc).

the webserver.xml is the tomcat config format. light and lean.
it maps directly to two primary objects in tomcat (i'll put
more of this in the discussion doc). the web.xml is the xml
which is context specific. if your familiar with the jswdk
WEB-INF/*properties today ... those will go away and be replaced
with a WEB-INF/web.xml.

this thread here is, in my mind, focused around server config
(webserver.xml) but it should be aware of component configurations
(web.xml) as an item on the radar but not perhaps in the center
of the screen at the moment.

- james